On Tue, May 21, 2024 at 7:10 AM Werner LEMBERG wrote:
>
> You want to position the 'f' sign into the staff lines of the upper
> staff? If yes, then it doesn't fit with the concept of a a `Dynamics`
> context *between* the staves IMHO. Instead, I would attach the 'f'
> sign to the upper staff, s
> Interestingly, the following does *not* work, [...]
It's not clear to me how the end result should look like.
> The dynamics context doesn't know that there's a staff above it
> and/ot the piano staff forbids the dynamics from encroaching on the
> staff above.
You want to position the 'f' si
On Mon, May 20, 2024 at 8:58 PM Werner LEMBERG wrote:
> Since version 2.25.13 the NR contains the attached warning box.
>
Thank you, Werner. Interestingly, the following does *not* work, but I can
kind of understand why. The dynamics context doesn't know that there's a
staff above it and/ot th
>> > So why would overriding the dynamic line spanner's
>> > outside-staff-priority change where the forte goes? Isn't it
>> > DynamicText? If anyone can clear this up for me, I would be very
>> > appreciative.
>>
>> When there are consecutive dynamics like \p \< ... \f \> ... \pp,
>> they need
On Mon, May 20, 2024 at 6:33 PM Jean Abou Samra wrote:
> > So why would overriding the dynamic line spanner's outside-staff-priority
> > change where the forte goes? Isn't it DynamicText? If anyone can clear
> this
> > up for me, I would be very appreciative.
>
> When there are consecutive dyna
> So why would overriding the dynamic line spanner's outside-staff-priority
> change where the forte goes? Isn't it DynamicText? If anyone can clear this
> up for me, I would be very appreciative.
When there are consecutive dynamics like \p \< ... \f \> ... \pp, they
need to be all vertically a
