Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(108)

Issue 4389047: Changes the Y offset callback of multi-measure rest. (Closed)

Can't Edit
Can't Publish+Mail
Start Review
Created:
13 years ago by MikeSol
Modified:
12 years, 9 months ago
Reviewers:
mike, cpkc
CC:
lilypond-devel_gnu.org
Visibility:
Public.

Description

Changes the Y offset callback of multi-measure rest.

Patch Set 1 : Changes the Y offset callback of multi-measure rest. #

Patch Set 2 : Changes function to account for breve rest #

Patch Set 3 : Fixes stupid mistake in output-lib.scm #

Unified diffs Side-by-side diffs Delta from patch set Stats (+27 lines, -9 lines) Patch
A input/regression/multi-measure-rest-y-offset.ly View 1 chunk +15 lines, -0 lines 0 comments Download
M lily/multi-measure-rest.cc View 2 chunks +0 lines, -8 lines 0 comments Download
M scm/define-grobs.scm View 1 chunk +1 line, -1 line 0 comments Download
M scm/output-lib.scm View 1 2 1 chunk +11 lines, -0 lines 0 comments Download

Messages

Total messages: 7
MikeSol
I was able to figure out a way to do this w/o an extra offset ...
13 years ago (2011-04-11 23:11:01 UTC) #1
cpkc_shaw.ca
On 11-04-11 05:11 PM, mtsolo@gmail.com wrote: > Reviewers: , > > Message: > I was ...
13 years ago (2011-04-12 04:32:12 UTC) #2
cpkc_shaw.ca
On 11-04-11 05:11 PM, mtsolo@gmail.com wrote: > Reviewers: , > > Message: > I was ...
13 years ago (2011-04-12 04:53:33 UTC) #3
mike_apollinemike.com
On Apr 12, 2011, at 12:32 AM, Colin Campbell wrote: > On 11-04-11 05:11 PM, ...
13 years ago (2011-04-12 10:11:11 UTC) #4
mike_apollinemike.com
On Apr 12, 2011, at 12:53 AM, Colin Campbell wrote: > On 11-04-11 05:11 PM, ...
13 years ago (2011-04-12 10:17:09 UTC) #5
MikeSol
The only (big) issue with this patch as it stands is that, at some point ...
13 years ago (2011-04-13 10:51:55 UTC) #6
mike_apollinemike.com
13 years ago (2011-04-13 12:05:27 UTC) #7
On Apr 13, 2011, at 6:51 AM, mtsolo@gmail.com wrote:

> The only (big) issue with this patch as it stands is that, at some point
> in the chain, the Y-offset of the multi-measure-rest is being fed into
> that which controls MultiMeasureRestText positioning.  Before, it would
> receive the Y-offset of 0, which did not bump these texts (i.e.
> fermataMarkup) up.  Now, it receives the new Y-offset, which causes
> these grobs to rise above their prior placement.
> 
> I don't really where this bumping-up of MultiMeasureRestText grobs is
> done...maybe Side_position_interface::general_side_position ?  Thoughts
> would be appreciated!
> 

After further reading, I get the sense that the issue comes from the fact that
the pure_relative_y_coordinate that an MMR needs to work is 0.0, and that the
shift of staff space can only happen after all of the positioning has been done
(read: in the print function).

It seems like the real problem is that
ly:side-position-interface::y-aligned-side is not the appropriate function for
MultiMeasureRestText #'Y-offset given how users likely want these grobs to be
typeset.  Try:

{
R1^\fermataMarkup
\override Staff . MultiMeasureRest #'Y-offset = #-1.5
R1^\fermataMarkup
\override Staff . MultiMeasureRest #'Y-offset = #0.5
R1^\fermataMarkup
\override Staff . MultiMeasureRest #'Y-offset = #1.0
R1^\fermataMarkup
\override Staff . MultiMeasureRest #'Y-offset = #2.0
R1^\fermataMarkup
}

IMO, the fermata should not move in any of these cases, or rather, its moving
should be a non-default behavior that can be requested by the user.

Assuming that others agree, I think that this should be fixed first before
tackling issue 1604.  And, if others agree, is there an existing function that
can achieve this behavior?

Cheers,
MS
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b