In general the items in a list control consist of a text description and an image. If you use images then you would normally have one for every item. Take a look at Windows explorer and switch between the various views to see how the 'standard' displays are laid out. One of these days I'm going to think of a really clever signature.

You are using MFC, so you don't need to handle PreTranslateMessage(). Just use the wizard to derive a class, use the message properties to add the WM_CHAR handler, and comment the line calling CDateTimeCtrl::OnChar(). Done with a few mouse clicks. All you need to type in using the keyboard is the name of the drived class, the comment chars, and replacing the CDateTimeCtrl by your class name in your code. The edit control of CDateTimeCtrl is not accessible. So it can't be done in the dialog. Even when it would be possible: It is always better to perform such things in the control rather than in the dialog. So it must be done only once and not within every dialog that uses such a control.

Like I *EDIT* my code for windows. Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.

Well spotted! Odd how it looked quite sensible when I wrote it. Unrequited desire is character building. OriginalGriff I'm sitting here giving you a standing ovation - Len Goodman

What you wrote looked fine to me; I just think the OP read more into it than you intended. Unrequited desire is character building. OriginalGriff I'm sitting here giving you a standing ovation - Len Goodman

Good tip. ============================== Nothing to say.

You can use CFrameWnd::GetActiveDocument. This returns the document attached to the currently active view. «_Superman_»  _I love work. It gives me something to do between weekends. _Microsoft MVP (Visual C++) Polymorphism in C

For the grid which have conditional formatting; I chose Ultimate Grid.

ProcDump[^] is an excellent tool for monitoring an application and generating stack dumps whenever something is wrong.

Don't forget to use a mutex (or something similar) to keep threads from accessing the CList simultaneously. That can cause major problems (that will be very hard to fix later on since its hard to diagnose a problem like this).

Thanks Niklas, Using a thread-safe container will be a good solution. I wish Microsoft should provide some in-built thread-safe containers. As currently there is no inbuilt thread-safe way so I will go for creating my own. But I will not be able to use it in this project because it is 90% completed and implementing a new container and replacing it over existing map will take a big code-patching. Thanks, I will take care this next time.

The only problem I see is the non-portability of writing the structure to the file instead of individual items. That is compiler structure [type] alignment dependent and may change from one compiler to the next or one version of the compiler to the next. Your solution sounds like a simple application of the KISS principle and avoids the problems of more complex solutions. Just add a header of some kind to the file. The header should contain an identifier, marking the file as the correct type, and a version number indicating the format type (a.k.a. data type [structure type]). This also has the advantage of being cross-language and cross-platform supportable. It sounds like all the data is read into memory at start up. In that case you only need one method (function) to read the file and convert it to the internal data structure at start up and one for writing it (if it has changed) out when shutting down. I used the above method in a commercial application (originally written in C) that supports file formats going back over 20 years. This is comparable to reading and writing Word or other document types that contain version specific format support. INTP "Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra "I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone

thanks Richard, you got the problem right. I am reading that article now.

thanks, I will read that :thumbsup:

Most likely the 32 bit EXE was given a local registry to play with, this is part of UAC legacy application handling. The 64 bit EXE is not seen as a legacy application, and gets a proper slap on the fingers. Usually it is during installation that one chooses what files should be opened with the application. Not something the application changes after installation.

Thanks I got it

Thanks Charles, I just checked out "Enable DPI Awareness" property does not come in VS2008. I will checkout in VS2010 tomorrow. Thanks for the reply, -Rahul

Can't understand why someone downvoted this. If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke [My articles]

Is that possible in C#?