Command Bars - Execute event does not always trigger

Print Page | Close Window

Execute event does not always trigger

Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Command Bars
Forum Description: Topics Related to Codejock Command Bars
URL: http://forum.codejock.com/forum_posts.asp?TID=3476
Printed Date: 04 November 2025 at 11:12am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Execute event does not always trigger

Posted By: dajv
Subject: Execute event does not always trigger
Date Posted: 05 January 2006 at 8:01pm

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.

Replies:

Posted By: Oleg
Date Posted: 06 January 2006 at 8:53am

Hello,

Can you send exceutable/your code to our issuetrack to debug it?

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS

Posted By: dajv
Date Posted: 08 January 2006 at 3:22pm

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.

Posted By: Oleg
Date Posted: 09 January 2006 at 10:30am

Hello,

We can't reproduce it, and nobody reported about it, so I guess you have some code in your application that can be reason of it.

-------------
Oleg, Support Team
CODEJOCK SOFTWARE SOLUTIONS