>>>>> "Dan" == Dan Niles <dan_at_more.net> writes:
>> 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.
Dan> I have narrowed the problem down.  The only windows that get
Dan> cycled are ones that have received focus since fvwm2 was started
Dan> or restarted.  Also, the order of cycling changes when you use
Dan> the mouse to give a window focus. I personally would prefer the
Dan> order to remain constant and predictable.
Yeah, I'll have to look into this...  It's still not quite right,
although it is better than 1.xx's circulate function.
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...
Dan> Works fine, great even.  The current version of FvwmAuto raises a
Dan> window when a window receives focus, so they work together well. The
Dan> only strange thing is that SloppyFocus is in effect even though not
Dan> specified.  This is ok because it is how one would expect ClickToFocus
Dan> to work: You click on a window to change focus.
Actually what I meant was that ClickToFocus should already be raising
the windows when you click in them, without the help of FvwmAuto.
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 Thu Apr 25 1996 - 09:15:56 BST