Text line hook does not invert with line position
Currently when a text line is added from the palette, it is placed above the staff. When I try to invert its position and put it under the staff, I expect the hook to invert its direction and point upwards, but it is still pointing downwards.
Am I doing something uncanonical? I failed to find a duplicate on the forum, so do please point me to the post if there is already an answer.
> MS ver.: 4.0.0
| Attachment | Size |
|---|---|
| 屏幕截图 2022-12-31 184952.png | 39 KB |
Comments
Why should it invert the hooks too?
In reply to Why should it invert the… by Jojo-Schmitz
... because the Line's position is now "Below" and the hook should point upward to the stave? That would presumably need a negative Height value for the hook, which is not available in the Properties tab.
In reply to ... because the Line's… by DanielR
My question was more why should that happen automatically rather than in a separate step
In reply to My question was more why… by Jojo-Schmitz
Well, not necessarily. Inputing a negative offset to achieve the effect is intuitive enough for me too. I suspect however that if negative offsets are generally not allowed, introducing it will break some paradigm the software is following I don't understand. Would you confirm that this is a reasonable function? If so, I'll try to write a feature request.
In reply to ... because the Line's… by DanielR
Thanks for confirming this is indeed the case. I never came to this need in 3.x so I didn't quite know if this is the case or the option is temporarily more difficult to find due to recent UI changes. I also find that built-in lines (e.g. the pedal line) indeed use a negative height (-1.6 by default), rather than a separate switch controlling the direction. After changing the value to a positive number by hand, the box prevents manually inputting negative values. I'm still unaware why there is this range clipping to begin with, so I'll investigate a bit further.
Made a PR (#15668 - Allow setting line hook heights to negative values). This seemes indeed to be introduced in 4.0, as the inspector has been re-designed. I hope this low-effort PR doesn't seem annoying, I'm just really new to the codebase.