Execute event does not always trigger

Gday,

I have been trying to track down this problem for a while. It cannot be reproduced reliably.

After a period of time ranging from 10 minutes to a couple hours of having our application open, eventually context menus no longer respond to mouse clicks. The user right clicks, the menu displays, but none of the controls in the menu respond.

I have been able to determine that when this happens, the Execute event is NOT being fired at all. The only thing that fixes it is restarting the application.

I have found that if I use the TPM_RETURNCMD flag then I don't get this problem, as I can force the calling of the Execute event. (When the above problem occurred I saw that other context menus that did not rely on the Execute event triggering (ie used TPM_RETURNCMD) did not suffer from the same problem.)

So the work around is to always use TPM_RETURNCMD, but would appreciate if you can you look into this, since it isn't ideal.

Well in theory you should be able to reproduce it with the CommandBars samples, so it wouldn't make a difference sending our code/executable (which I'm not permitted to do).

It is seemingly random - I have tried to reproduce it myself and cannot. It only seems to happen on non-development machines.

Perhaps you can review the code in question and examine how this could arise, if at all.