Hello, Looks like menus are indeed a little busted. You can't use both event models on a menu. You can use either the NEM or the OEM, but you can't selectively use NEM here and OEM there. If you add a menu to a window that is using the NEM and your window uses OEM, your menu won't work. Your menu's event model must match that of the window you're adding it into.
This is because menu commands are processed in their parent window's wndproc, and the wndproc assigned to a window depends on the event model it is using. A bit of bashing and hacking on my (and others) part could make multi-event-model menus work properly, but I'd like to know if this functionality is actually required by anyone. I mean, if you're a NEM user you're going to use the NEM for everything, and if you're an OEM user you're going to use the OEM for everything. So is there any point to allowing you to mix and match in menus? I'm inclined to believe "yes" just for flexibility, but if I discover that it looks too annoying to implement I might change my mind to "no". Steve
