[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5258 Vertical

From: Auto mailings of changes to Lily Issues via Testlilyissues-auto
Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5258 Vertical breve rest position in TabStaff/RhythmicStaff
Date: Sun, 14 Jan 2018 17:51:57 -0000

[issues:#5258] Vertical breve rest position in TabStaff/RhythmicStaff

Status: Started
Created: Sat Jan 13, 2018 04:47 PM UTC by Malte Meyn
Last Updated: Sat Jan 13, 2018 04:48 PM UTC
Owner: Malte Meyn

According to Gould breve rests should hang from a one line staff (RhythmicStaff) as semibreve rests do. Also, there is a comment in saying

// Staff position is somewhat icky regarding its definition for
// compatibility reasons.  It is intended to be the baseline of
// a breve rest.  However, when the staff space is more than
// single space (like with tablature), it looks better if all
// rests are actually hanging.  So staff position, in reality,
// is the semi-breve position - 2.  Everything else is
// calculated from there.

This confirms what Gould writes. But the code applies only to MMRs with a measure-count > 1.

That leads to inconsistent behaviour: MultiMeasureRest breve glyphs hang, but not for single measures. Rest breve glyphs don’t hang. Instead, all breve rests should hang.

\version "2.19.80"

music = {
  r1 R1 R\breve
  \time 4/2
  r\breve R\breve R\longa
  \time 8/2
  r\longa R\longa

\new TabStaff \with { \tabFullNotation } \music

\new RhythmicStaff \music

\new Staff \music

Sent from because address@hidden is subscribed to

To unsubscribe from further messages, a project admin can change settings at Or, if this is a mailing list, you can unsubscribe from the mailing list.

Check out the vibrant tech community on one of the world's most
engaging tech sites,!
Testlilyissues-auto mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]