well... As for messages goes, Windows define a default message handler for controls... You DON'T need to parse EVERY SINGLE message you get. The rule is simply.. if you are concerned about the event you are being informed then parse the message, otherwise just pass the message to the default message handler. By example, when the content of a text box is changed, your app get a notification message. Sometimes you'll need to check if the user wrote something valid but most of times you might not care about this so you just let the message go through the default message handler.
Is also important to understand that most
(all?
) interaction is done via messages.... if you want to add a single item to a listbox just send the LB_ADDSTRING Message TO THE LISTBOX ITSELF
(Every control is like a Window, you can actually send message to the controls too, and also get a handler as you do with any window or dialog
(actually winwatch get a handle to every control in a window to calculate the most adequate size to fit them all
)
BTW, Can you guess what the messages that start with LB_ are for??? For ListBoxes
lol
You WILL require to look at the SDK documentation very frequently unless you memorize every message and the parameters they receive... eVC help files are quite complete
(there are some things missing but nothing that google can't find
)
You'll send messages for adding things to a listbox, changing the text of a label or a button, putting a check mark to a CheckBox, set the current selection in a combobox, retrieve the text written by the user in a edit field, almost everything is done via messages so you MUST assimilate the concept very well....
[EDIT] These are just some simple explanations of things that are very important to understand in order to develop a windows application in C/C++
It's not a tutorial.. nor a manual, nor even a guide for programming...
Edited by ShadowMaster 2006-02-22 11:13 PM
and i'm interested... 
