Click event requires 2 clicks in 1.0.6.5

08-08-2003, 12:00 AM
Originally Posted By: Dan Marco<ipddmarco@earthlink.net>

I work on an application that was written in VB 6 and uses ActiveBar 1.0.6.5
. This is a mature application that has most of the kinks worked out of it
and would prefer not to take on the risk of upgrading to ActiveBar 2.
However, there is an outstanding issue that relates to ActiveBar 1.0.6.5.
In certain situations, when single-clicking an ActiveBar tool button, it
gets depressed and requires a second click to fire the click event. At one
point we were using 1.0.6.4 and upgraded to 1.0.6.5 to fix a different
problem but introduced this issue. We think it is due to 1.0.6.5 raising a
MouseExit event when clicking the button but does not bubble up to the Click
event for that button as it did in previous versions. Setting the UseHooks
property to False does not fix it like I thought it might. If anyone is
still using 1.0.6.5 and has run across this issue and has a solution, then I
would be very grateful. Also, if anyone has seen this problem in ActiveBar
2, that would be helpful in case we decide to upgrade.


Re: Click event requires 2 clicks in 1.0.6.5

08-11-2003, 12:00 AM
Originally Posted By: Jennifer-DD<activebar.support@datadynamics.com>

Hi Dan,

The issue Ive dealt with before is the click becoming non-responsive in AB
1.0. In this case setting UseHooks to false fixed the issue. Im sure your
aware we do not work on AB 1.0 anymore. Does this happen only under certain
conditions or environments? I know this issue does not happen in AB 2.0.
You can download a free evaluation and then apply the latest build 2.5.0.84
and test it if you'd like. I apologize for any inconvenience.


"Dan Marco" wrote in message
news:lX6jG%23dXDHA.2012@dynaweb.datadynamics.com...
> I work on an application that was written in VB 6 and uses ActiveBar
1.0.6.5
> . This is a mature application that has most of the kinks worked out of
it
> and would prefer not to take on the risk of upgrading to ActiveBar 2.
> However, there is an outstanding issue that relates to ActiveBar 1.0.6.5.
> In certain situations, when single-clicking an ActiveBar tool button, it
> gets depressed and requires a second click to fire the click event. At
one
> point we were using 1.0.6.4 and upgraded to 1.0.6.5 to fix a different
> problem but introduced this issue. We think it is due to 1.0.6.5 raising
a
> MouseExit event when clicking the button but does not bubble up to the
Click
> event for that button as it did in previous versions. Setting the
UseHooks
> property to False does not fix it like I thought it might. If anyone is
> still using 1.0.6.5 and has run across this issue and has a solution, then
I
> would be very grateful. Also, if anyone has seen this problem in
ActiveBar
> 2, that would be helpful in case we decide to upgrade.
>
>