|
You need to escape all backslashes in string literals - your path to game.exe doesn't do that.
|
|
|
|
|
try this
ShellExecute(m_hWnd,"open","C:\\Program Files\\myproj\\game.exe","", "", SW_SHOW);
Sethuraman.K - Bangalore
|
|
|
|
|
Hello Comunity,
i have an simple SaveAs dialog in my project to save some information in to files!
Ok,but i need some extra controls on this one,
is there any way to modify this standard SaveAs dialog?
E.g. add some new controls to this, button , checkbox, listbox etc.?
Thanks for any help!
regards
break;
|
|
|
|
|
Have you tried adding the control is the hook function? It's just a taad more complicated than creating your own (that resembles the standard one).
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Hello,
thanx for answer, no, i dont try nothing with hooks, that because i never do something with hooks,
but i hear about hook function, maybe i can find som instructions how to use hook functions?
regards
break;
|
|
|
|
|
Yes - you do this by creating a new dialog template and placing your new controls around special control/identifiers (stc1, stc2, etc.) that represent the standard controls on the interface.
Look up "Open and Save As Dialog Box Customization" in MSDN for more information.
Peace!
-=- James Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
|
Hello,
thanks for answer, i try to use one of the sugestions here...
regards
break;
|
|
|
|
|
Yes. See these articles for ideas:/ravi
|
|
|
|
|
Hello Ravi,
thanks for url's, i think the second link, easy image preview, is good stuf to beginn wit own sample!
regards
break;
|
|
|
|
|
Yes you can you need to stc1 here is articles about it 
|
|
|
|
|
Clickety[^]
-- modified at 23:40 Friday 9th February, 2007
Dario: How is "directory" in French? (I mean a file system directory).
John Simmons: "zee file holdaire thingie"
|
|
|
|
|
Which helps the OP how? 
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Ah you are right, I was sure he once wrote an article on it. Looking at the title, I just snatched(mistakenly) it. Oops, wait a min, I'll update the clickety.
Dario: How is "directory" in French? (I mean a file system directory).
John Simmons: "zee file holdaire thingie"
|
|
|
|
|
I have the following code :
class Test
{
public:
static const foo = 1;
static const bar = 2;
};
int _tmain(int argc, _TCHAR* argv[])
{
cout << Test::foo << endl << Test::bar << endl;
return 0;
}
- and absolutely no idea why it is working. I left the type declaration by accident and realized later that it shouldn't work - at least in my book. But it does. Can anyone explain that to me ? Is there some kind of default data-type for such situations ? If so, what is it ?
wbr Brainley
|
|
|
|
|
If you mean why does this get treated like a const int, that is because that is exactly what you created when you typed const foo.
I believe that int is treated as the default type in a scenaro like this, which is why you sometimes see code like unsigned uiABC = 0 to create an unsigned int variable.
Peace!
-=- James Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
|
I wonder if it would be treated as a QWORD on a 64-bit machine
|
|
|
|
|
Not if they keep the width of the int type at 32-bits... But I do not have a 64-bit environment handy...
Peace!
-=- James Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
|
WalderMort wrote: I wonder if it would be treated as a QWORD on a 64-bit machin
Probably.
int data type is environment specific which means that it's 16 bits wide in a compiler for 16-bit systems, e.g. the C-compiler for MicroChip PIC 18[^].
This is the standard, but a complier might not follow the standard.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
|
|
|
|
|
but the AMD 64-bit[^] docs specify that an int remains 32-bits in size. So I guess it really depends on how the compiler decides to interpret the code.
|
|
|
|
|
WalderMort wrote: but the AMD 64-bit[^] docs specify that an int remains 32-bits in size. So I guess it really depends on how the compiler decides to interpret the code.
Yep, very true.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
|
|
|
|
|
Is that MS-Specific or ISO ?
wbr Brainley
|
|
|
|
|
I think that is standard, or at least assumed. I have seen bits of older code, on older VAXen or U*ix boxes, that has things like:
static SomeVariable = 1;
unsigned SomeOtherValue = 0; Peace!
-=- James Please rate this message - let me know if I helped or not!<HR>If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles
|
|
|
|
|
Mr.Brainley wrote: and realized later that it shouldn't work
Why shouldn't it work?
It's static, meaning all instances share the same varialble, and it's const meaning it will never change. So it's perfectly safe to declare it as you have done.
|
|
|
|
|
WalderMort wrote: Why shouldn't it work?
No data type.
|
|
|
|
|
Yeah, in versions of VS prior to V2005, it will automatically assume you meant static const int foo = 1;
In VS2005, it'll give a sensible error (We found exactly this in some of our code when upgrading projects to 2005)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
