On Sat, Jan 19, 2002 at 11:24:46PM +0000, Mikhael Goikhman wrote:
> On 19 Jan 2002 15:33:15 -0600, FVWM CVS wrote:
> >
> > Log message:
> > * New events enter_window and leave_window in FvwmEvent.
>
> This does not work well with subwindows, even with frame / client window.
> Execute this config when you run any FvwmButtons:
>
> *FvwmEvent-AutoRaiseLower: PassId
> *FvwmEvent-AutoRaiseLower: enter_window "Silent FuncAutoRaiseLower Raise"
> *FvwmEvent-AutoRaiseLower: leave_window "Silent FuncAutoRaiseLower Lower"
>
> DestroyFunc FuncAutoRaiseLower
> AddToFunc FuncAutoRaiseLower
> + I WindowId $1 ("FvwmButtons") $0
> + I WindowId $1 ("any-other-app") $0
>
> FvwmEvent FvwmEvent-AutoRaiseLower
>
> The window is raised/lowered when you move the pointer from borders to the
> client window or from one buttons bar that contains a subwindow (pixmap,
> swallowed app) to another, i.e. more enter_window/leave_window are sent
> than needed.
It's the same if you have a mousey focus window under the pointer
that is not focused.
> Any fix for this?
I don't think so. Filtering Enter/LeaveNotify is by no means
trivial. If you have raise/lower bound to enter/leave, it's even
very easy to get two windows competing for the top position on the
stacking chain until the pointer leaves the area. It's
probably easier to enhance FvwmAuto to handle enter/leave instead
or in addition to focus_change.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
