Re: FVWM: Escaping calls to State and Infosostore in piperead

I Wrote earlier
"And why I don't use transient windows instead, well I have further
plans to use the state call - which I described shortly in my previous
post."

I used the wrong term here. I meant sticky, not transient.

And also - a few years ago I used sticky windows for that, but it was
something with the behavior of sticky windows that didn't fill my
needs - I don't remember what it was. But I decided to switch to
bookmarked_window.
And now I make the switch to states. which will take my config way
further from what it is today because I can have multiple states to
one window.

It's more about to explore and learn the advantages of whats possible
than find the simplest solution.

2018-12-26 19:26 GMT+01:00, Jaimos Skriletz <[email protected]>:
> On Wed, Dec 26, 2018 at 9:35 AM Peter Holm <[email protected]> wrote:
>>
>> This is more or less a follow up from my earlier question.
>> I have this
>> ---
>> Key             Space           A               M               State
>> $[infostore.transi] True
>> Key             Space           A               C               State
>> $[infostore.transi] False
>>
>> ..
>> AddToFunc StartFunction
>> + I InfostoreAdd  transi 31
>> ....
>>
>>
>> Then when I switch desk/workspace I  let the window(s) follow me
>
> Why not just use Sticky for this. No need to define a custom state to
> make it so windows move to a new workspace (pages/desktops) when you
> do.
>
> (sorry for the duplicate reply, forgot to CC the list)
>
> jaimos
>


-- 
Med vänlig hälsning / With kind regards
 ⼃Pᵉᵗᵉʳ Hᵒˡᵐ