Re: RemoveEmptyStaffContext erases previous setting

[Reinhold Kainhofer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 08 February 2010 16:24:57 you wrote:
> Would there be any disadvantages to replace Axis_group_engraver by
> Hara_kiri_engraver in the default definition of Staff, and just use
> \override VerticalAxisGroup #'remove-empty = ##t or ##f to switch
> between ordinary and RemoveEmpty versions? Is the book-keeping overhead
> in the Hara_kiri_engraver so large that it would increase the
> computational time significantly or could there be any other
> disadvantages. 
>
> This should be a much simpler solution than trying to fiddle with
> advanced Scheme stuff to work around limitations in the syntax.

Absolutely! So, is there any reason agains using Harakiri by default?


> I still think it's relevant to have a syntax difference between
> - Copy the current definition of context type Foo
> - Take settings from a variable called Foo

Yes, you are right that their syntax right now looks the same. However, how 
often do you really want to store a previous state of a context into a 
variable and reset the context later on? 

Most of the time, you rather want to define a set of context modifications to 
be 
applied at a later time (like in the RESC case), instead of completely 
restoring a context. Unfortunately, this feature is missing from LilyPond...

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: address@hidden, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * Edition Kainhofer Music Publishing, http://www.edition-kainhofer.com/
 * LilyPond music typesetting software, http://www.lilypond.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkt2s1oACgkQTqjEwhXvPN1HKwCePfekNbwxD30FcRX2r11wfViy
QPQAoMDYSdzMvb93vpXlcLEYcPdwYyKP
=x/UZ
-----END PGP SIGNATURE-----