in message <[EMAIL PROTECTED]>,
wrote Parv thusly...
>
> in message <[EMAIL PROTECTED]>,
> wrote fvwm-w thusly...
> >
> > On Sat, Oct 09, 2004 at 02:19:36AM -0400, Parv wrote:
> 
> > > Style  *  FPLenient \
> > >   , FPClickRaisesFocused      , FPClickRaisesUnfocused \
> > >   , FPClickDecorRaisesFocused , FPClickDecorRaisesUnfocused \
> > >   , FPClickIconRaisesFocused  , FPClickIconRaisesUnfocused \
> > >   , FPGrabFocus , FPReleaseFocus \
> > >   , FPAllowRaiseClickFunction \
> > >   , ClickToFocusPassesClickoff \
> > >   , ClickToFocusRaises , MouseFocusClickRaises \
> > >   , FPFocusByFunctionWarpPointer \
> > >   , MouseFocus
> > 
> > You should be aware that the maximum command length in fvwm is
> > 1024 bytes.  If you keep adding styles to this list you might
> > hit that limit at around 30 lines in the style definition.
> 
> I thought about that (as converting the above syntax w/ line
> continuations to "Style * " for each line undid some problem that
> turned out to be a red herring).

Not a herring after all!  After breaking up the above Style thusly ...

  Style  *  FPLenient \
    , FPClickRaisesFocused      , FPClickRaisesUnfocused \
    , FPClickDecorRaisesFocused , FPClickDecorRaisesUnfocused \
    , FPClickIconRaisesFocused  , FPClickIconRaisesUnfocused \
    , FPGrabFocus , FPReleaseFocus \
    , FPFocusByFunctionWarpPointer \
    , FPAllowRaiseClickFunction

  Style * ClickToFocusPassesClickoff , ClickToFocusRaises \
    , MouseFocusClickRaises , MouseFocus


... in 2.5.12, WindowList is making the list in the desired order just
like it does in 2.5.10 (w/ or w/o both combined).  Combining the two
styles does cause the problem (in 2.5.12).  Thanks Dominik.


BTW, comma placement has no effect on the order.  I understand that
the situation may change in future as Dominik has pointed out in this
thread and also previously in various threads.


  - Parv

-- 

--
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]

Reply via email to