Dominik Vogt <dominik.vogt_at_gmx.de> writes:
> 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?
I don't see one. I'm using Exceed 6.2.
> 2) FvwmEvent is doing this.
> 3) FvwmAuto is running and configured to do this.
Using FvwmAuto, Fvwm windows raise over native windows as they should.
Native windows don't raise over Fvwm windows unless you click on an
exposed part (as they should). Once a native window has focus,
an Fvwm window won't raise over a native window until I click on the
frame, or until I move from one Fvwm window into another. This makes
some sense, the first fvwm window to get focus doesn't know the native
window is in the way so it has no reason to raise itself.
I don't have any RaiseOverNative settings.
> 4) The application raises itself. This would mean that this
> occurs only for some applications.
> 5) Other reasons?
In Windows there is a TweakUI package that changes the focus model
from ClickFocus to PointerFocus. I had problems with it, so I'm not
using it. I don't know what that would do.
--
Dan Espen
444 Hoes Lane Room RRC 1C-214 E-mail: dane_at_mk.telcordia.com
Piscataway, NJ 08854 Phone: (732) 699-5570
--
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 - 10:13:47 BST