🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:

>> I'm wondering if my arbitrary 0x1234 WParamLo value
>> that isn't going to potentially run into conflicts with other
>> UI actions (e.g. menu items generated by VCL).
> 
> VCL menu items use their own provide HWND to handle their actions.  The
> WM_COMMAND for them will never go through your message handler.  

However, my WndProc() does receive WM_COMMAND messages other than the 
one that I am explicitly generating when my pop-up menu item is clicked.

My test application has, besides a button that triggers the pop-up in 
question, also some additional buttons that generate some output in a 
TMemo. Clicking on those buttons does generate several other WM_COMMAND 
events such as:
Message=00000111 - WParam=0000064E - LParam=0004064E

While clicking my Unicode Popup menu with 0x1234 WParamLo (the value is 
set via AppendMenuW) generates a WM_COMMAND like this:
Message=00000111 - WParam=00001234 - LParam=00000000

As you can see I am going to have potential problems with distinguishing 
between events from my own popup menu and from other events.

I am hoping you can clarify this behavior.

Thanks,

Kris