> The included sample system.fvwmrc & new-system.fvwmrc should be able
> to help. Basically, something like:
>
> Key Next A SCM Next [*] Focus
> Key Prior A SCM Prev [*] Focus
> Key Next A CM Next [!iconic CurrentScreen] Focus
> Key Prior A CM Prev [!iconic CurrentScreen] Focus
>
> *should* work just fine. I use the first two occasionally and haven't
> had any problems with them. I just tried the latter two, and they
> seemed to work ok...whoops, I take that back. It doesn't seem to be
> finding all the ones on the current screen, just the ones I've visited
> recently... This may be the problem. I'll have to look into that.
I have narrowed the problem down. The only windows that get cycled are ones
that have received focus since fvwm2 was started or restarted. Also, the
order of cycling changes when you use the mouse to give a window focus. I
personally would prefer the order to remain constant and predictable.
> Dan> (By the way, I am using FvwmAuto and ClickToFocus. ClickToFocus
> Dan> is not in the current documentation. Is SloppyFocus still
> Dan> supported?)
>
> Hm... I didn't think that FvwmAuto worked too well with
> ClickToFocus...
Works fine, great even. The current version of FvwmAuto raises a
window when a window receives focus, so they work together well. The
only strange thing is that SloppyFocus is in effect even though not
specified. This is ok because it is how one would expect ClickToFocus
to work: You click on a window to change focus.
Dan
--
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 Thu Apr 25 1996 - 09:06:45 BST