>>>>> "BAW" == Barry A Warsaw <bwarsaw_at_CNRI.Reston.VA.US> writes:
>>>>> "KG" == Kai Grossjohann
>>>>> <grossjohann_at_charly.informatik.uni-dortmund.de> writes:
KG> New behavior: Focus gives the window focus, WarpToWindow warps
KG> the mouse pointer into the window (without giving focus -- but
KG> there may be a side effect with MouseFocus).
BAW> There's a side affect with Focus now too. At least I see that using
BAW> WindowList to select another window does indeed move the focus to
BAW> it... temporarily. It quickly reverts to the window with the cursor.
BAW> Drag.
Damn.
Ok, this can be fixed, but we now have another problem - how to do it
and keep everyone happy.
Currently The built in window list has hard coded call to 'Raise_it'
(a built in function especially for the built in winlist it seems)
when it builds the menu.
I think I should make it call something like WinListFunc instead, and
make that be an interpreted function (with a default built up inside
of fvwm that just calls Focus and uniconifies if necessary). That way
WinListFunc could be added to or destroyed and recreated just like any
other interpreted function, and if people need or want the warp in
there (or would rather have the winlist execute a FvwmIdent or
something else) that could be added.
Does this solution sound acceptable to everyone? It might be
overkill, but I'd hate to just put an explicit warp in there and have
lots of people yell about it again.
Chuck
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Aug 06 1996 - 15:29:50 BST