-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Mittwoch, 27. Februar 2008 schrieben Sie: > This is just one of many situations, where you need to explicitly > create the Voice context yourself: [...] > This is a consequence of the way LilyPond creates new contexts on the fly, > if needed. So, I wouldn't classify it as a bug in cueDuring.
Okay, it's a general problem in lilypond ;-) Still, nowhere in the documentation can one find a hint that one needs to explicitly create the voice in this case. Even worse, all the examples for cueDuring do NOT create a voice explicitly (since none of the starts with cue notes, that's no problem, but typically one simply copies examples from the docs/lsr and adjusts them. How should one realize that an explicit voice creation is needed?) So, I think there should be a big fat warning in the cue notes section of the documentation and/or an LSR snippet about this. Cheers, Reinhol - -- - ------------------------------------------------------------------ Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD4DBQFHxUTBTqjEwhXvPN0RAh58AJjwY7FedCxrWIut/wyHgsY9wUikAKCaCVUR vbuf6GM7qQJPaG6bzcKdzQ== =zlxV -----END PGP SIGNATURE----- _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
