On Tue, Dec 10, 2002 at 10:58:31AM +0100, Dominik Vogt wrote:
> On Mon, Dec 09, 2002 at 11:10:48PM -0800, [EMAIL PROTECTED] wrote:
> > fvwm2 man page:
> > "The conditions are a list of keywords from the list below and are
> > separated by commas or whitespace."
> >
> > But, if I use commas in a list of conditions, I never get a match. If I use
> > spaces, it seems to work fine. Anybody else seen this behavior?
>
> Post an example so we can tell what goes wrong. I'd like to
> remove the non-comma syntax in the long run.
Works:
Key Tab A M SendToModule FvwmProxy Circulate \
Direction CycleEast (CurrentPage !Sticky)
Doesn't work:
Key Tab A M SendToModule FvwmProxy Circulate \
Direction CycleEast (CurrentPage,!Sticky)
I tried CirculateHit, but it doesn't seem to avoid WindowListSkip items.
Most of my persistant WindowListSkip items happen to be sticky, so this
works for me, but it's not really a good solution.
> > Also, if everybody is ok with the CycleWest, CycleEast, etc options
> > for the Direction command, I'll go ahead and add it to the core man page.
> > Any objections?
>
> I still think it should be moved into a separate command and take
> two directions as the argument (like IconBox). One major
> direction and a minor direction which must be orthogonal to the
> first one. For example:
>
> ScanWindows North West
>
> This means "Scan windows from North to South. Of all windows that
> are closest in the primary direction, pick windows from left to
> right."
I was also trying to minimize my impact of trampling around in the core.
A downside of my first version is that the secondary axis direction is fixed.
On the plus side, there's no new commands and only one function in one
file is changed.
Syntax-wise, ScanWindows looks fine. It just sounds like more code
(and therefore more time, space, and maintenence).
Is it code or syntax that's the problem? I haven't looked at the
parser/dispatcher, but if a short entry for ScanWindows can route
to the same CMD_Direction and F_CMD_ARGS has an argv[0] equivalent,
we can pretty much use the code close to what we have now.
If arg0==ScanWindows, I could do gravity_parse_dir_argument twice.
Or I guess we could just turn CMD_Direction into a regular function
and route CMD_Direction and CMD_ScanWindows into it.
I don't like how there are 8 possible secondary directions, but only
2 are valid. Maybe right/left turns, like 'ScanWindows East Right'.
That would mean the z-axis points into the screen.
--
_
( \ _ \ /_ / _ _ Jason Weber (503) 380-7424
\|(\/)())) \/\/(-/_)(-/( Infinite Monkeys Inc. Aloha, Oregon
// http://www.imonk.com/baboon [EMAIL PROTECTED]
(/ [EMAIL PROTECTED] [EMAIL PROTECTED]
"Canister contains at least 50% recycled material; 15%
post-consumer content."
-- Pringles Fat-Free (side of can)
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
