On Tue, Aug 07, 2001 at 01:05:22PM +0200, Olivier Chapuis wrote:
> BTW, I think that the change Xinerama{Enable,Disable} -> Xinerama
> is not very good: it is difficult to a configuration tool or a user
> new to Xinerama to know if Xinerama is enabled or not.
Er, what is the big difference between
XineramaEnable
XineramaDisable
and
Xinerama on
Xinerama off
? It just saves the additional commands. And I can't think of
any fvwm command that has an "off" and an "on" version. On the
other hand it makes module configuration a lot easier. Fvwm can
simply send the whole string after "Xinerama" to the module which
in turn passes it to a Xinerama library function to configure
itself. Also, many commands already use the boolean argument
type, so why not this one?
> With
> Xinerama{Enable,Disable} we know where we go as with the Xinerama
> command even an experimented user should try a command or an action
> to see if Xinerama is enabled or not and predict the effect of this
> command.
It almost never makes sense to turn off Xinerama anyway. If there
is only one screen it is a no-op. If you have more than one
screen, not using Xinerama support is a pain. The only situation
I can think of where this is not desirable is with a very big,
tiled screen composed of many monitors, e.g. on a trade fair. In
this case we can expect that the tech people are able to read the
man page.
Bye
Dominik ^_^ ^_^
--
Dominik Vogt, email: [EMAIL PROTECTED]
LifeBits Aktiengesellschaft, Albrechtstr. 9, D-72072 Tuebingen
fon: ++49 (0) 7071/7965-0, fax: ++49 (0) 7071/7965-20
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
