Trevor Daniels <t.daniels <at> treda.co.uk> writes: > > Mark Knoop wrote Monday, July 14, 2008 9:56 AM > > > On Mon, 2008-07-14 at 02:21 +0000, Carl Sorensen wrote: > >> Mats Bengtsson <mats.bengtsson <at> ee.kth.se> writes: > >> OK, I'll bite. > >> > Two good points. So why do we need \pointAndClickOn? > It is on by default, and can't be turned on once it > is turned off, so not then. If it is turned off in > the command line you'd hardly want to turn it on again > in the code, so not then either.
The only reason to have \pointAndClickOn is for consistency, I guess. I don't feel strongly about it. > > So, why not have just a single command? > > \noPointAndClick > > to override the default? That would be my preference. Perhaps \noPointAndClick would be better. However, there is a large body of predefined commands that is of the form \featureOn and \featureOff. For consistency I personally like \pointAndClickOff better than \noPointAndClick. However, if we need to emphasize the difference (that you can't have point and click on in part of your music and off everywhere else), then perhaps it's better to have an entirely different construct, so \noPointAndClick would be preferred. Carl _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
