Thomas Glanzmann <[EMAIL PROTECTED]> writes:
> > > 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.
>
> > Hrm. I used both times Maximise (one time called from FvwmEvent, the other
> time
> > called by my hotkey). I think that the problem is that the Maximize event f
> rom
> > FvwmEvent is to early for Gvim to handle.
>
> I have also a problem with xterm (it does not catch the resize command on a
> faster machine). So I did the following which solves the problem with gvim an
> d
> xterm. It is very ugly but it works. Maybe someone else has a better idea.
>
> (I added the + I Piperead "ls -al / &> /dev/null" which delays the the resize
> event)
>
> DestroyFunc AddWindow
> AddToFunc AddWindow
> + I Piperead "ls -al / &> /dev/null"
> + I WindowId $0 ("MAINscreen") FullScreen
> + I WindowId $0 ("LOCALscreen") FullScreen
> + I WindowId $0 ("DEVELscreen") FullScreen
> + I WindowId $0 ("CONSOLEscreen") FullScreen
> + I WindowId $0 ("Opera*") FullScreen
> + I WindowId $0 ("Gvim") FullScreen
> + I WindowId $0 ("Go to page") WarpToWindow 5 5
>
> *FvwmEvent-NewWindow: Cmd
> *FvwmEvent-NewWindow: PassId
> *FvwmEvent-NewWindow: add_window AddWindow
>
> AddToFunc StartFunction I FvwmEvent FvwmEvent-NewWindow
PipeRead "sleep 2"
or even better:
*FvwmEvent-NewWindow: add_window Schedule 2000 AddWindow
(Not tested.)
--
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]
