On 21/02/07, Michelle Konzack <[EMAIL PROTECTED]> wrote:
Hello,
While I was reading "man 1 fvwm" I have found "State state [bool]".
For what is this?
The State command (as well as a style condition) is useful in
"tagging" a window or groups of windows which themselves might not
logically be connected in anyway (such as via their Class or Resource
hint). Assuming you had three different windows which you wanted to
apply a common command to, such as iconify. You could use something
like this:
DestroyFunc IconifyMyWindows
AddToFunc IconifyMyWindows
+ I Next (AppA, !Iconic) Iconify
+ I Next (AppB, !Iconic) Iconify
+ I Next (AppC, !Iconic) Iconify
But the list would grow, obviously. The alternative might be to give
a window a state that FVWM could then track instead. You can do this
through Style lines:
Style AppA State 1
Style AppB State 1
Style AppC State 1
Then you can do:
All (State 1, !Iconic) Iconify
For instance. The "[bool]" part can be one of: "True", "False", or
"Toggle. I'll let you work out for yourself what those mean and how
they're applied.
I have this auestion because:
----8<------------------------------------------------------
The states have no meaning in fvwm, but they can be checked
in conditional commands like Next with the State condition.
----8<------------------------------------------------------
That just means the command doesn't influence FVWM directly. I don't
like the wording of it. It could be made to read less drastically, or
better yet dropped altogether. Maybe something like:
"States are best used in conjunction with conditional commands such
as: Next or All."
Would suffice.
-- Thomas Adam
