Re: Sticky popup menus

Donald Arseneau wrote:
> Brian Griffin <briang42@easystreet.com> writes:
>
>
>>Donald Arseneau wrote:
>>
>>> bind [winfo children %W] <ButtonRelease-1> {break}
>>> after 300 { bind [winfo children %W] <ButtonRelease-1> {}}
>>
>>Yes, there is a problem with menubuttons, but that problem is really in the
>>location of the posted menu, not a timing problem.
>
>
> No, it is a timing problem, in that the menu is posted faster than
> you can click the mouse. Sometimes the location makes the timing
> irrelevant, but sometimes a problem.

You have to break down the sequence of events to see that it is not a
timing problem. What's happening is that the menu gets posted such that
an active menu entry is under the mouse pointer as a result of the
<ButtonPress> event. Next, the posted menu takes over and its event
bindings are in effect. The <ButtonRelease> will perform it's required
action of invoking the active entry under the mouse. This is exactly
how it's supposed to work. The "bug" is that the menu should never ever
  be posted under the mouse; it should always be posted away from the
pointer. Period. When this does happen there is no problem. The menu is
"sticky" if the <ButtonRelease> is not over an active entry, or, if the
pointer is moved, the appropriate action is taken on the <ButtonRelease>
event.

I'm 99% certain the "placement" issue for menus has been fixed in 8.4.6.

-Brian
Received on Thu Sep 29 14:19:25 2005