2009/9/25 Duane Tarr <[email protected]>: > Hi, > > The initial placement of new windows can be such that a portion of the > window is off screen. I use SmartPlacement and MinOverlapPlacement.
I'd not bother with SmartPlacement to be honest if you're using MinOverlapPlacement. > Most often it is the bottom edge of the screen, but sometimes the new > window runs beyond the right edge. GVim in particular has this problem > as do some other applications (e.g., child windows of Thunar) also have > this problem. PlaceAgain always corrects the placement. Most > applications do not ever have this problem. So enable: BugOpts ExplainWindowPlaement on ... and make sure FVWM is logging to ~/.xsession-errors or some other file and send the results in when you see one of these windows go off-screen. > The problem occurs in 2.4.20 and 2.5.27. Not for me it doesn't, and this is using a completely blank config. > I have tried setting EWMHBaseStruts to values like 0 0 0 500, but to no > avail. I do not see anything else in the man page that looks relevant. Well you could only have set that value using FVWM 2.5.X which makes me suspect whatever is in your config for 2.4.X is causing the issue there as well. EWMHBaseStruts in this case is likely nothing more than a red-herring. > Here is what I think is the relevant part of my config. Ah. There's the problem then. "What you think" and "What is actually *needed*" are two different things. :) Please don't do that, just attach your entire fvwm2rc file, or use a pastebin or something. > EWMHBaseStruts 0 0 0 25 > Style * SmartPlacement,MinOverlapPlacement > Style * MinOverlapPercentPlacement,MinOverlapPlacementPenalties 1 2 0 1 0.05 And as you would expect, using just these values in a blank config yields no problems for me. So there's definitely something else in your config likely causing this which the above snippet isn't showing. Now, at a complete guess, you've so far mentioned: gvim thunar as programs causing you problems. They're both GTK applications, which means they're always going to be a royal PITA. Try setting: Style * !UsePPosition (Which is applicable to FVWM 2.5.X, if you want that for FVWM 2.4.X, use: "NoPPosition") If you don't know what that does, go look it up. -- Thomas Adam
