sorry for posting here, but I haven’t found any better place. I’m having problem which appeared after installation of the newest FVWM 2.6.3.
It seems, the module FvwmRearrange started to take the EwmhBaseStruts values in account. Am I right? Till now, I’ve been using the offset coordinates and the bounding box coordinates for “simulating” the proper EwmhBaseStruts behaviour.
Another thing I’m experiencing, newly created windows no more respect the EwmhBaseStruts area. I have no better description for that.
I use my configuration with minor changes for a longer time than 2 years. And I’m experiencing such a “non-trivial” problem for the first time.
Anyway, there is one more thing worth mentioning. FVWM gives me the following warning:
[fvwm][CreateConditionMask]: <<DEPRECATED>> Use comma instead of whitespace to separate conditions
for this syntax:
+ I Prev (CurrentGlobalPage, AnyScreen, !Iconic, !Sticky, !Layer $[fvwm_transient_layer]) \
Prev (CurrentGlobalPage, AnyScreen, !Iconic, !Sticky, !Layer $[fvwm_fullscreen_layer]) EWMHActivateWindowFunc
I can’t find anything about this in man pages. And I was too lazy to inspect the source code of FVWM.
Imho the best option would be, if the test-conditions could be used more than once in the Test command, e.g.
+ I Prev (CurrentGlobalPage, AnyScreen, !Iconic, !Sticky, \
!Layer $[fvwm_transient_layer], !Layer $[fvwm_fullscreen_layer]) \
This is now unfortunately impossible.
I would really appreciate your help.