Correct link]http://www.dumblob.hy.cz/pub/fvwm-mini.tar.bz2[/url]
No. Your domain is simply unreachable from here.
– Thomas Adam
I have to talk to my provider or something must be wrong with the content filtering in GB.
Does this link function http://ompldr.org/vYXR4eQ?
Fixed in CVS, the problem with CreateConditionMask. As for everything else with PositionPlacement, it’s again working as expected. In using your config, the windows are correctly placed.
– Thomas Adam
Thank you very much for that.
I made a short movie with my screen captured. Hopefully it helps. It is my first desktop recording, so please be patient.
http://ompldr.org/vYXUwNA/out.ogv
Right – there is still nothing wrong – the window, were it to be taken in to account for placement including the EWMHBaseStruts offset wouldn’t fit on the page – this is pixel perfect, therefore it’s placed above the EWMHBaseStrut range. Many users seem to think of this setting as some kind of brick wall – that’s just not true.
So that’s what’s happening.
Again, it’s working as intended. Are we done yet? This is really getting tedious.
– Thomas Adam
This, what you wrote is true. But I can make another movie with the same configuration, but older version (2.6.2) of FVWM and there the new window is placed “in” the EWMHBaseStruts area - the same window as you have seen in the clip.
I have two questions:
- Why does the new version (say 2.6.3 and newer) behave in this particular case differently?
- How can I mimic the old behaviour in the new version of FVWM?
The answer to the second one is of course much more important for me.
I’m really sorry about that, but I personally don’t know the FVWM as good as needed in this case - therefore I ask here, on the FVWM Forums.