I'm not sure whether this is a problem with my .fvwm2rc file, or with
fvwm2 (.0.41), and I don't remember seeing it mentioned on the list.
Anyhow, upon startup I have an xterm open, and it comes up underneath
the mouse. However, it doesn't get Focus until I move the mouse out of
the window and back in. Focus follows the mouse, SloppyFocus is on.
I was able to work around this by putting a Next[!iconic xterm] Focus
line in the init and restart functions, but then the cursor is in the
corner of the screen. So then I added a CursorMove to get it in the
middle of the xterm.
The problem with these workarounds is that they are slow. Everything comes
up, I'll start to move the mouse around, and then Focus/CursorMove hits.
This brings me to a couple of questions:
1) Why does Focus move the mouse to the top-left corner of the window? It
looks like it is finding the window and then generating a fake mouse
click to Raise the window. Could Focus be made to ignore the mouse?
2) If not, how about new command pair: SaveMousePosition and
RestoreMousePosition. I agree that it seems silly to add those for a
single problem, but I could see it being used in other places. Like
buttons that warp you to other desktops, and a "Back" button that
returns you to where you were, ala pushdir/popdir.
3) Or, as an alternative, how about saving the cursor position with the
window history. That way Next[] and Prev[] will have access to it, and
users can choose to restore the cursor position.
4) While I'm thinking about it, when we get more Style flags, how about a
StaysOnBottom? My xsession always starts last, so I have to explicitly
lower it. I'd rather not add a Next[xsession] Lower that will slow down
the startup even further.
-Eli
--
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 Mon Apr 15 1996 - 07:41:32 BST