Thomas Glanzmann <[EMAIL PROTECTED]> writes: > > I used FvwmIdentify. > > Thnx. > > > Here is the output of xwindow for a gvim window: > > > > home> xwininfo -size > > > > xwininfo: Please select the window about which you > > would like information by clicking the > > mouse in that window. > > > > xwininfo: Window id: 0x1c0007a "[No file] + - GVIM" > > > > Normal window size hints: > > Program supplied minimum size: 104 by 89 > > Program supplied base size: 20 by 61 > > Program supplied x resize increment: 7 > > Program supplied y resize increment: 14 > > Program supplied minimum size in resize increments: 14 by 6 > > Program supplied base size in resize increments: 2 by 4 > > No zoom window size hints defined > > > > Notice the resize increments. > > Its the remainders that are not getting covered. > > I can not follow you. You said that I can only resize a window by 14x6 > factors. Is that right? If I resize the window to fullscreen the gray area is > the remaining? But why does it work when I do it manually after the applicati > on > started up using Ctrl ALT F [1]. Even if I start gvim using the auto fullscre > en > stuff and press twice CTRL ALT F the gray area turns into a usable area. > > [1] Using CTRL ALT F to go fullscreen. > Key F W CM FullScreen > > DestroyFunc FullScreen > AddToFunc FullScreen > + I ThisWindow (!Maximized) Style $n BorderWidth 0 > + I ThisWindow ( Maximized, !"bluescreen") Style $n BorderWidth 1 > + I ThisWindow Maximize
I think maximize is using the resize increments and manual resize isn't. I don't know why. I'll try to check a little more, but maybe someone else on the list already has the answer. -- Dan Espen E-mail: [EMAIL PROTECTED] -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
