2009/1/26 Viktor Griph <[email protected]>: > On Sun, 25 Jan 2009, Thomas Adam wrote: > >> 2009/1/22 Thomas Adam <[email protected]>: >>> >>> I shall come up with something soon enough for review. Should be fun. >> >> And so I have. I've made "MapCommand" accept anything (i.e., a valid >> FVWM builtin, or a defined function) and in so doing have done the >> following: >> >> * Deprecate StartsRaised in favour of: Style foo MapCommand Raise >> * Deprecate StartsLowered in favout of: Style foo MapCommand Lower >> * Deprecate StartIconic in favour of: Style foo MapCommand Iconify >> * Deprecate StartNormal in favour of: Style foo MapCommand Iconify off >> * Deprecate StartShaded in favour of: Style foo MapCommand WindowShade >> dir >> > > What about the Layer, StaysOnTop, StaysPut and StaysOnBottom styles?
I'll add them to the list, in favour of using the Layer command outright with MapCommand as you say. > Not having checked the patch yet, one thing strikes me which can be > troublesome: What about windows created by programs grabbing the pointer. > Would forcing the use of complex functions for things that used to be doable > without them make some configurations impossible to recreate? It might, but I really don't want to open up the whole "NoGrab/Grab" discussion which were suggested on this list a while ago to avoid just this sort of problem. :) -- Thomas Adam
