Re: FVWM: New problems since 2.3.6

From: Dominik Vogt <dominik.vogt_at_gmx.de>
Date: Sun, 6 May 2001 14:46:31 +0200

On Thu, May 03, 2001 at 03:01:19AM +0100, Adye, TJ (Tim) wrote:
> Hi Dan,
>
> Thanks for the message.
>
> > Does clicking on the titlebar vs. clicking in the window act
> > differently?
>
> No, they do the same thing: clicking in window or titlebar both raise the
> window as one would like (in fact this is one of the improvements since
> 2.3.6, which often didn't raise the window if one only clicked in the
> window). The problem is that 2.3.31 is too eager to raise the window: when
> the active X-window is behind a native window, it is raised even if the
> cursor just passes through it. This is only a problem with the active
> window, and only when a native window is in front (when there's just
> X-windows involved it all works perfectly). Unfortunately this behaviour can
> make fvwm nearly unusable, as a small native window in front of a large
> X-window becomes nearly inaccessible as it's always pushed back when one
> tries to get at it.

I searched up and down the code but I can't find any way how
simply moving the pointer over the focused window could trigger
raising or lowering windows. You said that turning of the
RaiseOverNativeWindows option 'fixes' the problem. This proves
that the RaiseOrLowerWindow() function is called when the pointer
enters the window because it is the only place where the option is
evaluated. But fvwm does not call this function. I can think of
several possible explanations:

 1) Exceed raises the window. Is there perhaps some setting in
    Exceed for this?
 2) FvwmEvent is doing this.
 3) FvwmAuto is running and configured to do this.
 4) The application raises itself. This would mean that this
    occurs only for some applications.
 5) Other reasons?

> > > 2) Deiconising or switching to a window (by menu or taskbar) does an
> > > annoying full screen refresh. This doesn't happen when the window is
> > > selected by just clicking on it.
> >
> > I don't see this. Are you using some kind of function to
> > deiconify that includes a refresh?
>
> Not that I can tell. I'm using the sample-95 setup with a few edits. For
> example, I have
>
> *FvwmTaskBarAction Click1 DeiconifyFocusAndRaise
> AddToFunc DeiconifyFocusAndRaise I Iconify off
> + I Focus
> + I Raise

Please post your config file so we can try it out.

Bye

Dominik ^_^ ^_^

--
Dominik Vogt, dominik.vogt_at_gmx.de
Reply-To: dominik.vogt_at_gmx.de
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sun May 06 2001 - 07:46:59 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:51 BST