Dominik Vogt <[email protected]> writes: > On Fri, Aug 24, 2018 at 10:41:45PM +0200, hw wrote: >> Dominik Vogt <[email protected]> writes: >> >> > On Thu, Aug 23, 2018 at 07:10:47PM +0200, hw wrote: > [...] >> > Well, the full array of options to get shitty applications under >> > control is: >> > >> > Style ... fixedpposition, fixedusposition >> > Style ... fixedpsize, fixedussize >> > style ... gnomeignorehints, EWMHIgnoreStackingOrderHints >> > style ... EWMHIgnoreStrutHints, EWMHPlacementIgnoreWorkingArea >> > style ... EWMHIgnoreStateHints >> > >> > (The fixedus... styles make it impossible for the user to move or >> > resize the window too. If they re the only way to make the >> > application behave, one could make a script that waits for a few >> > seconds or until the windows appear and then remove the style.) >> >> Thanks! Alas, these options don??t have the desired effect with Firefox. >> >> What has an effect is TileManualPlacement (with FixedPPosition): With >> TileManualPlacement, I get to place the windows manually when Firefox >> starts. What I want is MinOverlapPlacement, or >> MinOverlapPercentPlacement. When I use either, the Firefox windows are >> placed on top of each other. > > Are you sure that the styles match? If windows would be created > without a name first, the style does not match, and firefox could > do with them what it wants.
Ok, let me try ... Style * MinOverlapPercentPlacement Style * FixedPPosition Style * !UsePPosition Style * gnomeignorehints Style * EWMHIgnoreStackingOrderHints Style * EWMHIgnoreStrutHints Style * EWMHPlacementIgnoreWorkingArea Style * EWMHIgnoreStateHints Style * DecorateTransient Style * !UseTransientPPosition No luck, the Firefox windows are still all placed at the top left corner. >> I was wondering if something is going on that prevents fvwm from >> noticing for the placement that there are windows already there when >> Firefox suddenly creates its three because it is creating them too fast >> or somehow not entirely. Yet getting to do manual placement when >> TileManualPlacement is used would indicate that fvwm does realise that >> these windows are being created. >> >> The manual placement fvwm falls back to, when TileManualPlacement is >> used, would indicate that fvwm can not find a smart location for these >> windows. > > You mean as a command or as a style? I mean the placement policy as a style, falling back as described in the manual: ,---- | TileManualPlacement | | This is the same as TileCascadePlacement, but uses ManualPlacement as | the fall-back method. `---- That means I do get to manually place the windows when I use TileManualPlacement instead of MinOverlapPercentPlacement or MinOverlapPlacement. I can also see the windows being cascaded on top of each other when I use TileCascadePlacement. I'm finding it suspicious that two placement options work only half-way and two others do not work at all. All these options do have in common that for all of them, the part which is not working is the part where fvwm is supposed to figure out where to place the windows *depending on which other windows they would cover*. It is like fvwm can not figure out that there are windows, or does not consider them when figuring out the placement. >> What could be causing this? Is Firefox somehow claiming the entire >> screen because it tries to place the windows itself, making fvwm figure >> there is no good place to put them? Without FixedPPosition, the windows >> are still being placed on top of each other. >> >> I??ll resort to TileManualPlacement for now because it??s easier to place >> the windows where I want them as they are created than it is to move >> them once they??re all there. >> >> > There's also the option >> > >> > bugopts explainwindowplacement on >> > >> > Which will print a detailed report to the console when new windows >> > are placed. >> >> You mean the FvwmConsole module? Nothing is printed there when I enable >> this and place any window. > > No, in the output of the X server, wherever that goes. After trying to get systemd to create log files, it apparently goes into /var/log/Xorg.0.log (where it might have gone to before). Alas, no output is added to the log file when I use this option and create windows. Do I need to set compile time options for fvwm to make this work? It seems it must be "true" rather than "on", but that doesn't seem to give any output, either.
