Re: Some wild considerations and a question

[Thomas Morley]

Am Mo., 19. Okt. 2020 um 08:40 Uhr schrieb Jacques Menu <imj-muzhic@bluewin.ch>:

> We often have to add things such as short skips and cadenzas to avoid having 
> so-called events at the exact same time moment in the score.
> This is illustrated by \HiddenMeasureAndBarLine in the attached file: 
> commenting its use out at line 47 shows the problem.
>
> Would it be meaningful, useful and not too hard to implement, to allow for 
> several events at a given time moment, and a way to sort them depending on 
> the user's needs? This would make it possible for the user to control the 
> order in which LilyPond would handle events occurring at this time moment.
> If so, such a feature could be added to the above wish list…

Well, the problem arises, when _conflicting_ commands are set by the user.
Examples
(1)
{ R1 \bar "." \break \bar "[|:" R1 }
Well, lily could warn here...
But the problem can be solved nowadays, because the bar-line-code was
ported from C++ to guile some time ago ;)
(2)
{ \time 3/4 \time 6/8 R2. }
Well, lily could warn here...
There is scheme-code available to get the graphic output.
But what about the other settings a \time-command will cause? How to
decide which should take preference?
(3)
simultaneous RehearsalMarks
There are several scheme-codings available.
See LSR or the afaik latest here:
https://codereview.appspot.com/577180043/
(My own take on it)

In general, "a way to sort them depending on the user's needs" is
always difficult.

Cheers,
  Harm