Re: FVWM:
On Sat, Jan 05, 2019 at 01:27:38AM +0100, Peter Holm wrote: > Is it possible to add an already started application (for example > xterm) to fvwmbuttons.? Yes -- how are you thinking of doing that? Would it be by clicking a button in FvwmButtons? > Or is it better to use FvwmIconMan .? I don't get how to get > FvwmIconMan to use numbered states. FvwmIconMan has nothing to do with FvwmButtons. > Reason to ask - I have managed to make some grouped windows which I > want to add a buttonbar to, or on the fly or add and remove the > windows into FvwmButtons, and ther have a Button.Panel for the > windows. > Best would be if I could get the buttons to show up in the same order > as the windows is layered. Sounds as though you want to use FvwmIconMan then. -- Thomas Adam
FVWM:
Is it possible to add an already started application (for example xterm) to fvwmbuttons.? Or is it better to use FvwmIconMan .? I don't get how to get FvwmIconMan to use numbered states. Reason to ask - I have managed to make some grouped windows which I want to add a buttonbar to, or on the fly or add and remove the windows into FvwmButtons, and ther have a Button.Panel for the windows. Best would be if I could get the buttons to show up in the same order as the windows is layered. Here is the main part of the config for my grouped windows. - AddToFunc StartFunction + I InfostoreAdd tabbs 29 ... Key T A SM ToggleWindow ThisWindow DetachWindow ThisWindow AttachWindow # ToggleWindow is planned to be used for much else, for example -right now with correct # parameters It is used to stick and unstick single or grouped windows. # I guess I will rewrite this function a few times DestroyFunc ToggleWindow AddToFunc ToggleWindow + I ThisWindow (CurrentPage, State $[infostore.tabbs]) + I TestRc (Match) KeepRc $[0] $[1] + I TestRc (NoMatch) $[2] $[3] # + I TestRc (Error) DestroyFunc AttachWindow AddToFunc AttachWindow + I None (State $[infostore.tabbs]) + I TestRc (Match) SetMainWindowSpecs + I ThisWindow State $[infostore.tabbs] True + I ThisWindow (State $[infostore.tabbs]) ResizeMoveMaximize $[infostore.TabWindow_Width]p DestroyFunc SetMainWindowSpecs AddToFunc SetMainWindowSpecs + I InfoStoreAdd TabWindow_Width $[w.width] + I InfoStoreAdd TabWindow_Heigth $[w.height] + I InfoStoreAdd TabWindow_X $[w.x] + I InfoStoreAdd TabWindow_Y $[w.y] DestroyFunc CycleWindows AddToFunc CycleWindows + I Next (CurrentPage, State $[infostore.tabbs]) Raise ... #Also some functions for manage the position of grouped or not grouped windows. ... Key 1 A SM ToggleWindow "All (CurrentPage, State $[infostore.tabbs])" LeftUpper\ ThisWindow LeftUpper Aside from my question, any comments or suggestions regarding this config are highly welcomed. -- Med vänlig hälsning / With kind regards /Peter Holm
Re: FVWM: Escaping calls to State and Infosostore in piperead
> Aside from avoiding asking the more obvious question of why you want to do it > this way, .. I just remember why I didn't like to use sticky windows for that. I just don't want to accidentally unstick any of those windows I randomly use to have floating around. Earlier I switched to use BOOKMARKED_WINDOW, but since I like to mark multiple windows in cthe same way one can do with toogle the sticky-ness, I asked in an earlier post how to do that. Jaimos Skriletz pointed me to use states - so now I hope to go that way full out. > ...there's.no code change required. The above is wrong -- don't > quote > '(State 31)' as this will throw the parser out. Try: > > All (State $[infostore.transi]) MoveToPage -1p -0p > > -- Thomas Adam > I can't get it to work that way. But as I now got infostore to work in the piperead, I feel I can live with that I need to use quotes until I find out why it not work as you described. -- /Peter Holm
Re: FVWM: appearance
On Fri 2019-01-04 13:11 , Mandar Mitra wrote: > I haven't used Fedora in a very long time, but once upon a > time, rpm -qa --last would give you a list of packages in > most-recently-installed/updated-first order. That should give > you some hint about what might have changed. (To list the dnf (rpm) transactions, and possibly even undo some of them, one can use the dnf transaction history facility, as I've mentioned earlier in this thread.) m.
