Thank you very much!!! I've enjoyed a lot. Regards, Ryan :cool:

Hi, Thanks for your code. :-) Regards, Ryan

[binary sorting using GDI+] >> looking forward to a code snippet! It was written without a smiley since your original post lacked a smiley. I hoped that you'd understand that if your original comment was a joke, this was also. I left my smiley out in case you were serious. > I'm sorry, is all humour lost on you ? Absolutely not! :-) I'm sorry if I offended you, it was never my intention. As you suspected, my post wasn't to be taken too seriously, it was just the lack of smileys that got me into rant-mode. :-) It might also be that I'm a not too frequent visitor here, whey I couldn't possibly know you're an "STL zealot". Good to know though, and now I'll remember it! :-) Cheers, /Mike

For MFC programmers, an important distinction is whether a DLL is an MFC Extension DLL or not. It is certainly true that a regular DLL can be C++ specific to the extent of being incompatible with other languages such as Visual Basic, but what is important is that MFC classes can be shared between EXEs and DLLs only when the DLL is an MFC Extension DLL. See MFC "TN011: Using MFC as Part of a DLL" and "TN033: DLL Version of MFC".

Thank you!!! Regardz -Rya

I think a DLL unloads from physical memory when this memory it's needed. As when Windows loads a DLL, it only reserves the virtual memory and maps it to the DLL. If the DLL was not loaded, when the process access it, it causes a page fault, and automatically Windows loads it into physical memory. I suppose the it's the same process when unloading: removing the DLL from memory if RAM it's not needed is a silly task, as maybe Windows must reload the DLL after removing it. I suppose the RAM pages containing the DLL will be marked as they can be used, but if anybody uses this pages, 'reloading' the DLL into physical memory will be a little effort. If I find more information I'll post another message, or if anybody can assure this or correct me, will be pleased!!! :)

"Essential COM" .... For a beginner, hmmmm. Sorry Alex but.... yes I learned a lot from the Essential COM book. heck, I always thought that Don invented COM.. ***BUT*** In the first 4 times :O I have tried to read the book I always get stuck on the fifth chapter... where Don suddenly speaks in different language I believe Essential COM is a great book. However it is not for beginners (at least not all chapters) I recommend, an easier path before digging into Essential COM. like "Understanding DCOM " by William Rubin and Marshall Brain. Then digging into "Essential COM" "Essential COM" is a great book, read it after you get your self familiar with the basic concepts first. I did. This is my Story and I am sticking to it :) Alfadhly

Hello! Include a handler for WM_KILLFOCUS message in your CWnd derived class that you use for subclassing edit box. in this handler you have to call SetFocus function to gain focus back to the control. Alternatively you can handle EN_KILLFOCUS notification in the edit box' parent window. In the handler for the notification you have to do the same - set focus back to the edit box using SetFocus() function. Regards, Andrei Zenkovitch Dundas Software