Viktor Griph <[email protected]> writes: > Den mån 27 aug. 2018 00:27hw <[email protected]> skrev: > >> With Firefox, I think using FixedPPosition, !UsePPosition fix it as >> well, but the problem is that for some reason, fvwm does not place the >> windows according to the placement policy. > > As you describe it it sounds as if Firefox maps the new window before > restroing the size of the window, so Fvwm will do it's placement logic > based on whatever sixe firefix has put on the windows when they are > displayed,
What does it mean to "map" a window? Does fvwm not know the size of a window before placing it? > and once placed, Firefox rezises the windows to the old > size. As far as I can see, the windows created by Firefox are each 1/3 the width of the display and full height of the display when they become visible. Apparently, they are not being resized --- unless I can not see that happening. > (It should be obvious from the ExplainWindowPlacement option if > that's the case.) If I could only get that to work ... :) > You can also try to use the "PlaceAgain" comman on the Firefox windows > once they are all restored and see if they pace as you expect then. If > so, you might be able to do some magic with FvwmEvent to trigger a > PlaceAgain automatically on Firefox windows, but I'm not certain it is > possible, or how to configure the module to do it. Interestingly, this option does nothing to the windows of Firefox, and they remain on top of each other. It replaces other windows as expected, though. Oh, and when I manually move the Firefox window which is on top and replace it then, it is being moved to the top left corner of the display so it ends up on top of the other two windows! How come? There must be some bug with fvwm that it can not correctly place the windows of Firestorm.
