Re: FVWM: ANDing Style options

2007-03-09 Thread Thomas Adam
On Fri, Mar 09, 2007 at 05:13:36PM -0500, [EMAIL PROTECTED] wrote:
 All:
 
 Is there a way to AND together Style options?

That happens by default, unless two conflicting styles collide, which
which case their ORed; the last one specified being used in that case.

Now, if you supply an example of what it is that's not happening, that
might be better.

-- Thomas Adam

-- 
Wanting to feel; to know what is real.  Living is a lie. -- Purpoise
Song, by The Monkees.



Re: FVWM: ANDing Style options

2007-03-09 Thread Ryan Daly
On Fri, 2007-03-09 at 22:26 +, Thomas Adam wrote:
 On Fri, Mar 09, 2007 at 05:13:36PM -0500, [EMAIL PROTECTED] wrote:
  All:
  
  Is there a way to AND together Style options?
 
 That happens by default, unless two conflicting styles collide, which
 which case their ORed; the last one specified being used in that case.
 
 Now, if you supply an example of what it is that's not happening, that
 might be better.

Well, what I'd like to do is:

Style Evolution  Enter Password for  TileCascadePlacement

That way the window (whose class is Evolution and whose title is
Enter Password for) gets the TileCascadePlacement.

Currently my config is:

Style Evolution   TileCascadePlacement
Style Evolution-alarm-notify  TileCascadePlacement

That's making all Evolution windows get TileCascadePlacement.  I'd
like to have it so TileCascadePlacement only applies to certain
Evolution windows.




Re: FVWM: ANDing Style options

2007-03-09 Thread Thomas Adam
On Fri, Mar 09, 2007 at 06:43:01PM -0500, Ryan Daly wrote:
 On Fri, 2007-03-09 at 22:26 +, Thomas Adam wrote:
  On Fri, Mar 09, 2007 at 05:13:36PM -0500, [EMAIL PROTECTED] wrote:
   All:
   
   Is there a way to AND together Style options?
  
  That happens by default, unless two conflicting styles collide, which
  which case their ORed; the last one specified being used in that case.
  
  Now, if you supply an example of what it is that's not happening, that
  might be better.
 
 Well, what I'd like to do is:
 
 Style Evolution  Enter Password for  TileCascadePlacement
 
 That way the window (whose class is Evolution and whose title is
 Enter Password for) gets the TileCascadePlacement.

Right.  You can't do that currently, although there is a branch in FVWM
which has an experimental version of applying styles conditionally to
windows where the title and/or class, and/or resource is matched; but it
breaks compatability.

 Currently my config is:
 
 Style Evolution   TileCascadePlacement
 Style Evolution-alarm-notify  TileCascadePlacement
 
 That's making all Evolution windows get TileCascadePlacement.  I'd
 like to have it so TileCascadePlacement only applies to certain
 Evolution windows.

Find something unique about them if there is anything.  Specify the
general style at the top, and then mitigate any windows you don't want
to apply with a different style.  That's as good as you're going to get
to doing.

-- Thomas Adam

-- 
Wanting to feel; to know what is real.  Living is a lie. -- Purpoise
Song, by The Monkees.



Re: FVWM: ANDing Style options

2007-03-09 Thread Ryan Daly
On Fri, 2007-03-09 at 23:49 +, Thomas Adam wrote:
  Style Evolution  Enter Password for  TileCascadePlacement
  
  That way the window (whose class is Evolution and whose title is
  Enter Password for) gets the TileCascadePlacement.
 
 Right.  You can't do that currently, although there is a branch in FVWM
 which has an experimental version of applying styles conditionally to
 windows where the title and/or class, and/or resource is matched; but it
 breaks compatability.
 
  Currently my config is:
  
  Style Evolution   TileCascadePlacement
  Style Evolution-alarm-notify  TileCascadePlacement
  
  That's making all Evolution windows get TileCascadePlacement.  I'd
  like to have it so TileCascadePlacement only applies to certain
  Evolution windows.
 
 Find something unique about them if there is anything.  Specify the
 general style at the top, and then mitigate any windows you don't want
 to apply with a different style.  That's as good as you're going to get
 to doing.

Will do.

Do you know how soon the experimental branch you refer to above is going
to make it to the unstable or stable code?