Using MFC, you can make an SDI application, and make the view descend from a CListCtrlView. Set it to large icon view, and you're part of the way there.
Choosing the text / icons is another challenge. Pick a directory, and use FindFirstFile etc to get all the *.exe files there? Extract the icons from each of them?
Then handle the double click / enter events to say "aha, the user has chosen one!". Then launch the application. As you say you don't want to a run a program, then I don't know what you mean by it. But I'm sure it's explainable.
Basically, just break this down into smaller parts.
First, the listview SDI app, and fill it with a couple of hardwired words / icons.
Second, get a list of the programs / thingies you care about.
Third, give them appropriate pics.
Fourth, work out how to handle enter key / double clicking on one.
Lastly, lauch the application the use picked.
I have a menu with a combo box as one of its item. The combo box has 4 entries. When I compile and run my application I find that the each entry in the combo box gets repeated. So my menu shows 8 combo box entries instead of 4. Why is it so?
Also while running the application in debug mode, the combo box is blank when I launch the menu. But in release mode, the first combo box entry appears as default value. I want to avoid this.
Please suggest me a solution for the above 2 problems.
I have created a custom control to diaplay a rather compilcated bitmap on the main window. Now I can trap every message I need except for the WM_EXITSIZEMOVE, and this is probably the most important of them all.
I only want to resize the bitmap after the user has finished resizing the main window. I can re-create the effect by sending a message to the control from the main window, but this defeats the purpose of having a custom control in the first place.
Is there any way to detect when the parent window has completed a resize?
Yes, it was a NCHITTEST issue, I was returning the wrong value.
Nomatter what I tried, I just cannot trap the WM_EXITSIZEMOVE.
I am going to have to take Chris' approach and set a flag on a WM_SIZE event. But since I will only recieve mouse messages when the mouse is over the window I will have to use some type of timer. Luckily for me though, I have a thread running to monitor any changes required in the bitmap.