Not confusing at all! I think things are getting clearer. This is my main initial confusion. Window Procedure A window procedure is a function that receives and processes all messages sent to the window. Every window class has a window procedure, and every window created with that class uses that same window procedure to respond to messages. The system sends a message to a window procedure by passing the message data as arguments to the procedure. The window procedure then performs an appropriate action for the message; it checks the message identifier and, while processing the message, uses the information specified by the message parameters. I think the key confusion for me is what Windows considered a "CLASS". pasztorpisti, thanks again but can you clarify something for me? When you say "(not window messages!!!)" your not talking about "WM_*" messages but messages that are specific to a class like "BM_*", "LB_*", "CB_*", and ...?

I think this answers your question, http://docs.oracle.com/javase/1.5.0/docs/guide/language/annotations.html[^] Quote: Once an annotation type is defined, you can use it to annotate declarations. An annotation is a special kind of modifier, and can be used anywhere that other modifiers (such as public, static, or final) can be used. By convention, annotations precede other modifiers. Annotations consist of an at-sign (@) followed by an annotation type and a parenthesized list of element-value pairs. The values must be compile-time constants. Personally never used annotations for anything other than generating Java Docs and I'm not sure what your trying to use it for here? Are you really trying to define an interface?

that's 4 statements not a single one it is going to look something like this. int array[3] = {99,100,88};

Working on a Win32 C++ (non-MFC) application and I've run into an issue that I can work around but from reading the MSDN documentation I shouldn't have to do this. I'm under the impression that a child window for example:

CreateWindowEx(WS_EX_CHIENTEDGE,
TEXT("LISTBOX"),
TEXT("DEVICES"),
WS_CHILD | WS_VISIBLE | ...
10,10
mainWindowHandle,
(HMENU)IDC_DEVICELISTBOX,
mainWindowInstance, NULL)

should pass all messages to its parent message queue and should be processed in its parent's WndProc callback message? This does not function like this in my application so I have to use "GetWindowLong" and "SetWindowLong" to define a callback message for each control child window. I've seen a lot of examples but I'm still not clear if my application is working as expected or if I'm just stressing out over nothing. Thanks for any help in advance.