true; got me

Are you sure TRUE is defined as 1? I know in MFC it is, but I've seen implementations that use the definition #define FALSE 0 #define TRUE (!FALSE) I don't see how this could be the cause of your problem, but it might add to it. Also, have you checked the type BOOL is in fact defined as int and not overwritten by some old header? Wouldn't be the first time I've seen conflicting macro definitions... You could of course overcome such issues by explicitely defining an int variable that holds the intended value: void SetOrder(BOOL bOrder) { int iOrder(bOrder?1:0); _itot_s(iOrder, ... P.S.: I just checked the definition of the not operator '!', and it appears my above example #define TRUE (!FALSE) would in fact result in the definition #define TRUE true (provided you have a modern C++ compiler that supports the type bool). In a context that requires an int, true would be converted to 1 as required by the standard, so the concern I brought up can in fact not be a problem at all, and my workaround is uncalled for. modified on Friday, April 1, 2011 10:41 AM

resize : you mean dynamically ? or only when the dialog is created ? if dynamically, then, Windows User Experience Guidelines says that you need a border to be able to "grab" to something to resize the dialog, and that's only for resizing the dialog frame, not moving and repositioning the content which you will have to do manually. If you really need to have no border for your dialog, then you need something to "anchor" the mouse position and handle the mouse movements to compute the new dialog frame size. for example (in pseudo-code ) : in the handler for LBUTTON_DOWN for the dialog , get and store the mouse position (A) and capture it (Get/SetCapture) in the handler for LButtON_UP, get the current mouse position (B); compute the difference between A anb B and resize the dialog (SetWindowPos) with the computed diffference. ... good luck with that. Watched code never compiles.

Krauze wrote: I find it kinda weird that this function sometimes works but sometimes not. And in those instances where it does not, are you calling GetLastError() to find out why? "One man's wage rise is another man's price increase." - Harold Wilson "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons "Man who follows car will be exhausted." - Confucius

you are welcome.

https://cfx.svn.codeplex.com/svn/Visual%20Studio%202008/CppShellKnownFolders/ReadMe.txt[^] see links to msdn articles mentioned there also.

I prefer to avoid using the heap when it's not necessary: It's faster, safer and helps minimise heap fragmentation. Steve

Thank y'all!

thx a lot

you have got a couple mistakes on the line file.Read( &str, 3 ); First of all str by itself is provides a pointer, so there is no need to put the ampersand in front of it. Secondly, you are reading 3 bytes, but your buffer is only 3 bytes. You will have no room for the terminating zero character, although one may be supplied by the file itself. The code should be: file.Read( str, 2 ); str[ 2 ] = '\0'; Refer to MSDN for further information http://msdn.microsoft.com/en-us/library/ctka0kks%28v=VS.80%29.aspx[^]

In fact Ive tried this method later. And it works perfectly.

a really good idea!

Now that's the type of message I would rate a 5. Not due to the geographical insinuations. Nor the musical references. I don't really know, but it just appeals to me. home

In fact there's a fault in my codes when dynamically loading GetModuleFileNameEx(). But Ive corrected it. So it can perfectly run now. What I need to do now is just to add exception handlers. Thank yall.

1. Create a memory DC 2. Select your image into it 3. Blit to the paint DC (of the dialog) 4. Unselect the image from mem DC home

Really thx! In fact, pDC->MoveTo() isn't needed cos the GDI defines the starting point as the left-top automatically. And I use rc.DeflateRect(0,0,1,1); Thus the borders are all visible.

Thank y'all! I've got it solved with the help of DavidCrow. Actually, ::GetCurrentDirectory() may return inconsistent paths.