>> Or maybe there is a bug somewhere? I think not having to think
>> about the order would be quite beneficial.
>
> I totally agree there, but the New_fingering_engraver has been
> designed that way and it's complicated enough. It'd be great of
> course if someone had a good idea how to get ri
Am Di., 10. März 2020 um 00:07 Uhr schrieb Torsten Hämmerle
:
>
> Thomas Morley-2 wrote
> > Any hints why this error is generated and how to avoid?
>
>
> Hi Harm,
>
> Unfortunately, applying \consists "New_fingering_engraver" does not quite do
> the trick yet, because there's a problem of sequence:
Werner LEMBERG wrote
> Interesting. Is it documented somewhere that the order of `\consists`
> calls is relevant (sometimes)?
Hi Werner,
I couldn't find anything about that in the documentation.
When experimenting with Voice and TabVoice, I noticed that Voice worked
without a problem and, most
> In order to avoid this problem of sequence, I've first removed
> Script_column_engraver and appended it again /after/
> New_fingering_engraver. Looks funny but actually solves the
> problem.
>
> [...]
> \remove "Script_column_engraver"
> \consists "New_fingering_engraver" % *before* Script
Thomas Morley-2 wrote
> Any hints why this error is generated and how to avoid?
Hi Harm,
Unfortunately, applying \consists "New_fingering_engraver" does not quite do
the trick yet, because there's a problem of sequence: it needs to come
*before* Script_column_engraver, that's why just appending
Hi all,
if I want to print StrokeFinger in TabStaff I need to consist
"New_fingering_engraver". And it works fine, at first sight...
Alas, if there is an additional markup then I get a programming error
(even if the markup isn't printed at all).
\version "2.20.0"
\new TabVoice \with { \consists
