enable buttons

No, Manko, no silly flamethread; I'll resume what's happened.
"code" posted a request, that sounded to me as a non-sense one. What does exactly mean "enable grayed buttons *by hiew*"?

When a control is created, and it's enabled, (otherwise you can always use a resource editor, and not hiew, anyway - you could, but this is desperately out of the code's reach, I guess), its state is usually settled by an EnableWindow call. I never found an application that behaved in a different way (not so about menuitems, anyway). So, if you put a breakpoint on that function, sooner or later you will land inside the proper code, no matter where it is placed (inside the main EXE, inside a DLL, inside any runtime created code, etc.). By varying in real time the "bEnable" parameter, you will often be able to discover which call handles your control. That's all, and this was synthesized in my replies, to code and to LOUZEW.

Maybe my knowledge is somehow inadequate, maybe not, but...why this attitude? Can you honestly say that the sarcastic part of the thread was initiated by me?

If you maintain that my knowledge is lacking, supplying with further elements is information, but criticizing with no information sounds insulting. Is this statement wrong, Manko?

Regards