First, please, please!! use plain text while providing code.
Following the link above I see no code at all, neither in Gilbertos initial mail to the list.
On topic:
\crossStaff reverts the style property, but not a stencil set by the user. Those stencils, predefined in flag-styles.scm mostly don't read the style-property at all. As opposed to the stencil defined in C++, iiuc, and the default-flag defined in the same .scm-file
So what's the proper fix?
(1)
One could simply temporary set the stencil to #no-flag in crossStaff.
(2)
Or one could return an empty stencil for every scheme-defined stencil, if style is 'no-flag.
That would mean to change normal-flag, mensural-flag, flat-flag, old-straight-flag and modern-straight-flag as defined in flag-styles.scm.
The there defined default-flag looks at this condition already.
Ok, a completely independent user defined flag-stencil will likely not look at the style-property, but we could make the procedures predefined in flag-styles.scm respecting it. A complete new code is in the responsibility of the programmer anyway.
So, I lean to (2), looks cleaner to me to give style 'no-flag more or less the same weight as stencil #no-flag.
But maybe I overlook something.
Opinions?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Issue 5026: \crossStaff mangles all grace note flags.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2017-01-02
Patch: new --> needs_work
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2017-01-02
Fails make check on the 'flags-default.ly' regression test:
...Parsing...Renaminginputto:`/home/jlowe/lilypond-git/input/regression/flags-default.ly'/home/jlowe/lilypond-git/input/regression/flags-default.ly:73:29: error: GUILE signaled an error for the expression beginning here \override Flag.stencil = # no-flagInterpreting music...Preprocessing graphical objects...Interpreting music...Preprocessing graphical objects...Interpreting music...warning: type check for `stencil'failed;value`#<unspecified>' must be of type `stencil'Preprocessinggraphicalobjects...Calculatinglinebreaks...Drawingsystems...Calculatinglinebreaks...Drawingsystems...Calculatinglinebreaks...Drawingsystems...Writingheaderfield`texidoc' to `./2d/lily-1e423b1e.texidoc'...Writing./2d/lily-1e423b1e-1.signatureWriting./2d/lily-1e423b1e-2.signatureWriting./2d/lily-1e423b1e-3.signatureLayoutoutputto`./2d/lily-1e423b1e.eps'...Layout output to `./2d/lily-1e423b1e-1.eps'...Layoutoutputto`./2d/lily-1e423b1e-2.eps'...Layout output to `./2d/lily-1e423b1e-3.eps'...Writing./2d/lily-1e423b1e-systems.texi...Writing./2d/lily-1e423b1e-systems.tex...Writing./2d/lily-1e423b1e-systems.count...Writingtimingto2d/lily-1e423b1e.profile...Unboundvariable:no-flag
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
commit 27f9ebef47a058db8befc5cb05bd63375144fc01
Author: Thomas Morley thomasmorley65@gmail.com
Date: Mon Jan 2 14:12:42 2017 +0000
Issue 4983 Let crossStaff hide non-default-style flags
Return empty-stencil for all flags using the code provided in
flag-styles.scm, if the style property is 'no-flag as set by
the crossStaff-function.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I had a look into it.
First, please, please!! use plain text while providing code.
Following the link above I see no code at all, neither in Gilbertos initial mail to the list.
http://lilypond.1069038.n5.nabble.com/cross-staff-chords-do-not-automatically-hide-non-default-flags-td195328.html
worked, yes, but it's tedious to search which archive displays what...
On topic:
\crossStaff reverts the style property, but not a stencil set by the user. Those stencils, predefined in flag-styles.scm mostly don't read the style-property at all. As opposed to the stencil defined in C++, iiuc, and the default-flag defined in the same .scm-file
So what's the proper fix?
(1)
One could simply temporary set the stencil to #no-flag in crossStaff.
(2)
Or one could return an empty stencil for every scheme-defined stencil, if style is 'no-flag.
That would mean to change normal-flag, mensural-flag, flat-flag, old-straight-flag and modern-straight-flag as defined in flag-styles.scm.
The there defined default-flag looks at this condition already.
Ok, a completely independent user defined flag-stencil will likely not look at the style-property, but we could make the procedures predefined in flag-styles.scm respecting it. A complete new code is in the responsibility of the programmer anyway.
So, I lean to (2), looks cleaner to me to give style 'no-flag more or less the same weight as stencil #no-flag.
But maybe I overlook something.
Opinions?
(2) sounds good and consistent to me.
Issue 4983 Let crossStaff hide non-default-style flags
Return empty-stencil for all flags using the code provided in
flag-styles.scm, if the style property is 'no-flag as set by
the crossStaff-function.
http://codereview.appspot.com/315330043
Here a generic test-code:
While working on this I noticed wrong behaviour of graces:
Replace the above "B = ..." with
to see no Flag for the grace-note.
Worth another ticket.
Issue 5026:
\crossStaff
mangles all grace note flags.Fails make check on the 'flags-default.ly' regression test:
Fix 'no-flag'-stencil
http://codereview.appspot.com/315330043
Passes make, make check and a full make doc.
Patch on countdown for Jan 8th
Patch counted down - please push.
pushed to staging as:
commit 27f9ebef47a058db8befc5cb05bd63375144fc01
Author: Thomas Morley thomasmorley65@gmail.com
Date: Mon Jan 2 14:12:42 2017 +0000
I have verified that the code in https://sourceforge.net/p/testlilyissues/issues/4983/#731a works now.