>>>>> "MB" == Mark Boyns <boyns_at_sdsu.edu> writes:
MB> I just tried the patch and it only works a little better for
MB> me. It seems to only do the right thing when there are no
MB> windows that accept focus on the second screen. For example:
MB> screen0: nothing screen1: xterm screen2: nothing
MB> If I move the mouse out of the xterm on screen1 and onto
MB> screen2, the xterm cursor is no longer solid and focus appears
MB> to really be on screen2. (I use sloppyfocus)
MB> But, if the screens are like this:
MB> screen0: nothing screen1: xterm screen2: xterm
MB> When I move the mouse out of the xterm on screen1 and onto the
MB> blank screen on screen2 (not touching the xterm on screen2),
MB> focus is still in the xterm on screen1.
MB> Anything else I can try?
I use MouseFocus, and just tried SloppyFocus. Looks like some things
are getting in the way, and I'll have to look at it more closely. The
question is, should SloppyFocus force the old window to retain focus
even when the cursor crosses a screen boundary? I'm not sure and I
don't like SloppyFocus much. I'd be interesting to hear what other
multi-headed users think, then I can try to debug the 2-screen
situation (although Mark or others will have to help with #screens >
2).
-Barry
--
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 Fri Oct 04 1996 - 17:03:05 BST