lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: \stopStaff \startStaff bug


From: Jean Abou Samra
Subject: Re: \stopStaff \startStaff bug
Date: Sat, 7 Jan 2023 17:03:22 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0

Le 07/01/2023 à 16:48, Kieren MacMillan a écrit :
Hi all,

[  It sometimes makes me wonder if we need a concept of "infinitesimal
time", to allow disambiguating  ]

Yes, the concept of 0-cycles, that can be allowed to execute in order for 
decisions to be made at the end of the timestep once all the 0-cycles have 
completed, seems like a good idea.
That might even be a liminal space in which the infamous Grace Music Bug™ could 
be handled grace-fully…?



Actually, that is what originally made me muse about this ...

Issue #34 is, in my opinion, a perfectly unsolvable problem, because
it's asking LilyPond to guess things that can't be determined with
certainty from the user input, and it is practically impossible in
general to guess these without reading the user's mind. Therefore,
my preferred way of handling it would be to add a command sparing
the need to compute the duration of the grace group, as a way
to replace grace skips.

<<
  { \grace { c'8 d'8 } c'1 }
  {
    \once \override Staff.TimeSignature.color = "red"
    \grace s4 % => \dt  ???
    \once \override NoteHead.color = "red"
    c'1
  }
>>


If we additionally require the user to add \dt (or grace
skips) when there is such an ambiguity, by emitting a
warning/error in such cases, there will be no confusion for
users, and the problem will be kind of solved, even if not
in the way that most people would like but is in fact
hardly possible.

Again: implementation handwaving, and I'm definitely not
going to look at this anytime soon.

Best,
Jean

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]