Issue 135 in project lilypond
Issue 135: markup on spacer rests doesn't obey \emptyText http://code.google.com/p/lilypond/issues/detail?id=135 Comment #5 by hanwenn: removed inspection of X-extent of papercolumn in this case. Issue attribute updates: Status: Fixed Labels: fixed_2_11_16 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 135 in project lilypond
Issue 135: markup on spacer rests doesn't obey \emptyText http://code.google.com/p/lilypond/issues/detail?id=135 Comment #4 by gpermus: My reading of the discussion in bug- is that this is a feature request. Here's two relevant quotes: quot;What's the best way to specify that a TextScript attached to a spacer note does not occupy any horizontal space (meaning that the bar lines are placed at the same place as if you didn't have the text)?quot; (there appears to be none) Han-Wen: perhaps the best thing is to switch of the use of column-gt;extent (X_AXIS) as a measure for spacing. This has already caused lots of problems. Sorry to keep on un-invalidating this bug report, but I don't want this info to get lost. Issue attribute updates: Status: Accepted Labels: -Type-Defect Type-Enhancement -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 135 in project lilypond
On 1/22/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Issue 135: markup on spacer rests doesn't obey \emptyText http://code.google.com/p/lilypond/issues/detail?id=135 Comment #3 by hanwenn: To make object partake in vertical skylining, it needs outside-staff-priority. This is not the problem: TextScripts have outside-staff-priority by default. The problem is that the proposed workaround breaks outside-staff positioning because the outside-staff positioning algorithm thinks the TextScript has empty X-extent so it won't collide with anything. In other words, there isn't a way to make a TextScript over a spacer rest take up no space without causing other side-effects (or at least, no one has thought of a way yet). ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 135 in project lilypond
Joe Neeman escreveu:
On 1/22/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135
Comment #3 by hanwenn:
To make object partake in vertical skylining, it needs
outside-staff-priority.
This is not the problem: TextScripts have outside-staff-priority by
default. The problem is that the proposed workaround breaks
outside-staff positioning because the outside-staff positioning
algorithm thinks the TextScript has empty X-extent so it won't collide
with anything. In other words, there isn't a way to make a TextScript
over a spacer rest take up no space without causing other side-effects
(or at least, no one has thought of a way yet).
no, it actually is the problem. If you add the propery outside-staff-priority
to MultiMeasureRestText, R1^\markup{ bla } actually does the right thing.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 135 in project lilypond
On 1/22/07, Han-Wen Nienhuys [EMAIL PROTECTED] wrote:
Joe Neeman escreveu:
On 1/22/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135
Comment #3 by hanwenn:
To make object partake in vertical skylining, it needs
outside-staff-priority.
This is not the problem: TextScripts have outside-staff-priority by
default. The problem is that the proposed workaround breaks
outside-staff positioning because the outside-staff positioning
algorithm thinks the TextScript has empty X-extent so it won't collide
with anything. In other words, there isn't a way to make a TextScript
over a spacer rest take up no space without causing other side-effects
(or at least, no one has thought of a way yet).
no, it actually is the problem. If you add the propery
outside-staff-priority
to MultiMeasureRestText, R1^\markup{ bla } actually does the right thing.
Mats' example used multimeasure rests, but the original question was
about spacer rests. Unless I've misunderstood, there is still no good
answer to the question
What's the best way to specify that a
TextScript attached to a spacer note does not occupy any horizontal space
(meaning that the bar lines are placed at the same place as if you didn't have
the text)?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 135 in project lilypond
Han-Wen Nienhuys wrote:
Joe Neeman escreveu:
On 1/22/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135
Comment #3 by hanwenn:
To make object partake in vertical skylining, it needs
outside-staff-priority.
This is not the problem: TextScripts have outside-staff-priority by
default. The problem is that the proposed workaround breaks
outside-staff positioning because the outside-staff positioning
algorithm thinks the TextScript has empty X-extent so it won't collide
with anything. In other words, there isn't a way to make a TextScript
over a spacer rest take up no space without causing other side-effects
(or at least, no one has thought of a way yet).
no, it actually is the problem. If you add the propery outside-staff-priority
to MultiMeasureRestText, R1^\markup{ bla } actually does the right thing.
Please read again the text I wrote, which is quoted in the
bug report. The typesetting problem I want to solve is to
have a text script (or whatever text ... grob) that is left aligned
with the beginning of the measure, when there is a multimeasure
rest. Since there is no really good way to obtain this with
LilyPond today, you should see the bug report as a feature
request.
/Mats
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 135 in project lilypond
Mats Bengtsson escreveu: Please read again the text I wrote, which is quoted in the bug report. The typesetting problem I want to solve is to have a text script (or whatever text ... grob) that is left aligned with the beginning of the measure, when there is a multimeasure rest. Since there is no really good way to obtain this with LilyPond today, you should see the bug report as a feature request. perhaps the best thing is to switch of the use of column-extent (X_AXIS) as a measure for spacing. This has already caused lots of problems. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 135 in project lilypond
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135
Comment #2 by gpermus:
I haven't seen a response to Mats' email (on Jan 3, 2007) on the subject, so I'm
adding it here and marking the bug unresolved.
Mats wrote:
Can we turn this into a question: What's the best way to specify that a
TextScript attached to a spacer note does not occupy any horizontal space
(meaning that the bar lines are placed at the same place as if you didn't have
the text)?
The best I can come up with is
\override TextScript #'X-extent = #'(0 . 0)
However, this means that it isn't taken into account in the new fancy
collision avoidance.
A common situation where this is useful is when you have a tempo change
at a bar line and the instrumental part begins with a multi measure rest.
The following example illustrates four different solutions. The last one
is the only one that gives a really nice output, but I find it a bit embarrasing
for LilyPond that you can't get this layout without using such an ugly hack.
\version quot;2.10.0quot;
\relative c''' {
c1
% Nice handling of the text but wrong rest.
r1^\markup{quot;Andante moltoquot;}
c1
% The text affects the bar lines
lt;lt; R1 s1^\markup{quot;Andante moltoquot;} gt;gt;
c1
% Better, but the collision handling doesn't work
\once \override TextScript #'X-extent = #'(0 . 0)
lt;lt; R1 s1^\markup{quot;Andante moltoquot;} gt;gt;
c1
% Desired layout, but ugly tweaks in the input:
lt;lt; R1 \once \override Rest #'transparent = ##t r1^\markup{quot;Andante
moltoquot;} gt;gt;
c1
}
Issue attribute updates:
Status: Started
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 135 in project lilypond
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135
Comment #1 by hanwenn:
Disagree about this being a bug.
emptyText sets constraints ('rods').
In the absence of anything else (ie. notes), lily
has to use some basis for guessing a space. It does
so by taking the width of the papercolumn object,
which is wide due to the fooo text.
---gt;8
\version quot;2.9.28quot;
\layout{
indent=0.
line-width=3.\cm}
\relative c' {
\emptyText
c1\noBreak
s1^\markup{quot;fquot;}
c1
}
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Text scripts on spacer notes. Was: Issue 135 in project lilypond
Can we turn this into a question: What's the best way to specify that a
TextScript attached to a spacer note does not occupy any horizontal space
(meaning that the bar lines are placed at the same place as if you
didn't have
the text)?
The best I can come up with is
\override TextScript #'X-extent = #'(0 . 0)
However, this means that it isn't taken into account in the new fancy
collision avoidance.
A common situation where this is useful is when you have a tempo change
at a bar line and the instrumental part begins with a multi measure rest.
The following example illustrates four different solutions. The last one
is the only one that gives a really nice output, but I find it a bit
embarrasing
for LilyPond that you can't get this layout without using such an ugly hack.
\version 2.10.0
\relative c''' {
c1
% Nice handling of the text but wrong rest.
r1^\markup{Andante molto}
c1
% The text affects the bar lines
R1 s1^\markup{Andante molto}
c1
% Better, but the collision handling doesn't work
\once \override TextScript #'X-extent = #'(0 . 0)
R1 s1^\markup{Andante molto}
c1
% Desired layout, but ugly tweaks in the input:
R1 \once \override Rest #'transparent = ##t r1^\markup{Andante
molto}
c1
}
/Mats
[EMAIL PROTECTED] wrote:
Issue 135: markup on spacer rests doesn't obey \emptyText
http://code.google.com/p/lilypond/issues/detail?id=135
Comment #1 by hanwenn:
Disagree about this being a bug.
emptyText sets constraints ('rods').
In the absence of anything else (ie. notes), lily has to use some
basis for guessing a space. It does
so by taking the width of the papercolumn object,
which is wide due to the fooo text.
---gt;8
\version quot;2.9.28quot;
\layout{
indent=0. line-width=3.\cm}
\relative c' {
\emptyText
c1\noBreak
s1^\markup{quot;fquot;}
c1
}
Issue attribute updates:
Status: Invalid
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
