On 2015/01/27 07:26:53, dak wrote:
It seems to me like this number-pair consists of two settings that
would almost
always be adjusted independently. Wouldn't it make more sense to make
a
separate property here? That way, the user would not need to remember
and
restate the setting he is no
Aaaand another thought: wouldn't it make more sense instead of having
independent shifts for "with other articulations" and "without other
articulations" when the articulation closest to the notehead is
responsible for aligning the whole stack of articulations?
Which would be the extreme case of
It seems to me like this number-pair consists of two settings that would
almost always be adjusted independently. Wouldn't it make more sense to
make a separate property here? That way, the user would not need to
remember and restate the setting he is not interested in.
https://codereview.appsp
Are you sure there is a cycle?
Rest_collision::calc_positioning_done now uses the pure
height of rests because the height of certain rests depends
on their position on the staff, which Rest_collision is
responsible for adjusting.
Rest_collision does use the height of the rests to determine the
Reviewers: ,
Description:
Rest_collision::calc_positioning_done now uses the pure height of
rests because the height of certain rests depends on their position on
the staff, which Rest_collision is responsible for adjusting.
There are differences in regression test output that I can not yet
expl
LGTM, thanks!
https://codereview.appspot.com/196260043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reviewers: ,
Message:
Please review.
Description:
Issue 2535: Staccato on stem side alignment when other articulations are
present
The default positioning of staccato dots in combination with other
articulations
is poor, because the dot is positioned midway between the center of the
note head
a
As requested I've changed the issue description.
Peter C
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello,
Here is the current patch countdown list. The next countdown will be on
January 29th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=pat
Patch on countdown for Jan 29th
https://codereview.appspot.com/194090043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Patch on countdown for Jan 29th
https://codereview.appspot.com/190530043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
11 matches
Mail list logo