Hi Werner, On Thu, Feb 27, 2025 at 1:04 PM Werner LEMBERG <w...@gnu.org> wrote:
> > >> What is the current recommendation for aleatoric notation? > >> Specifically, a group of cells to be performed in any order the > >> player wishes. > > > > A few changes are needed. The attached should work for you: > > Very nice! Thanks! > While adapting the code to 2.25 and playing around I > noticed the following comment in the contained example: > > ``` > %% Uncomment dynamic: box is sized to accommodate, but dynamic > %% is pushed aside. > g8%\p > ``` > > What exactly is meant with 'accommodate'? Should there some vertical > space be reserved for the 'p' sign within the frame? If so, it seems > not to work: an activated `\p` is positioned outside of the frame, and > no space is reserved. > Yes, some space should be the default, and my comment was invalidated by some changes I made within the engraver. I've attached a revision of the file for which the comment does again make sense. The engraver now acknowledges objects with the dynamic-line-spanner-interface. > A bit later in the example there is a commented-out fermata; after > making the fermata active there is indeed such a vertical space > reserved, and prefixing `\fermata` with `\tweak outside-staff-priority > ##f` makes the fermata actually become part of the frame. > Interestingly, in the revised file, this tweak isn't needed for scripts, but a tweak is needed to get the dynamic into the box: \tweak DynamicLineSpanner.outside-staff-priority ##f In the interest of simplicity of use, I wonder if there is a way to get the engraver to behave in a natural way without needing to tamper with outside-staff-priority here! Best, David
frameEngraver.ly
Description: Binary data
