On Tue, Jan 18, 2000 at 01:00:30PM +0000, neil.bird_at_rdel.co.uk wrote:
> Neil Bird wrote:
> > Dominik Vogt wrote:
> > > No, you *can* toggle it back. The 'maximised' state is only turned
> > > off when you *resize* the window, not when you move it. Try it out,
> > > it works.
> > So it does - fantastic!
>
> Except - to get it to work from a bound Function:
>
> AddToFunc Down-Maximise \
> "I" Maximise $0 $1
> + "I" WindowId $w (!Maximized) Move 0w -0
>
> ... will *only* work in a binding. OK, that's fair enough. If I
> FvwmCommand it, the Maximise asks for the window to be clicked upon, but
> the WindowId command won't know what window that was. Doesn't matter.
Actually you can rewrite your function like this:
AddToFunc Down-Maximise
+ I Maximize $0 $1
+ I Move 0w -0
In theory this function should ask for a window to operate on once
and then use it for 'Maximize' and for 'Move', but apparently is
doesn't. Seems to be a bug.
Bye
Dominik ^_^
--
Dominik Vogt, Agilent Technologies, Dept. BVS
Herrenberger Str.130, 71034 Boeblingen, Germany
phone: 07031/464-4596, fax: 07031/464-3883, dominik_vogt_at_agilent.com
--
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 majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Jan 18 2000 - 07:52:19 GMT