Re: [PATCH] mensural rests vertical alignment

[Han-Wen Nienhuys]

address@hidden writes:
> 
> 
> On Thu, 21 Mar 2002, Han-Wen Nienhuys wrote:
> 
> > ...
> > I have  one big problem with this patch. It adds a lot of complexity
> > to the rest-engraver, only for the sake of mensural rests. That is not
> > acceptable. Practically speaking, I don't understand why this stuff
> > has to be in the translator section. Why can't we have extra
> > grob-formatting functions that deal with mensural rests? Formatting
> > stuff should go into the back-end, not in the engravers.
> >
> 
> Ok, but the vertical position depends on
> 
> (1) the range of pitches of preceeding and (not yet implemented)
>     succeeding note heads.  This probably should be done by setting proper
>     grob properties while processing the music (acknowledge_grob (),
>     process_music ()), so this code must go into the engraver.
> 
> (2) the vertical position of the neighbouring rests (at least the nextmost
>     rest to the left side) plus additional status information, that is
>     needed while processing a sequence of rests, such as the current
>     direction of the zig-zag line.  Hence, there really should be an
>     instance (just like the rest engraver) that is capable of processing a
>     sequence of rest grobs in a single function call.  Is this possible in
>     the back-end?  Are there any examples of this kind?


No not yet, but it seems to me that the solution is to store pointers
to next and preceding notes in the rests, and then do the formatting
in the backend.



-- 

Han-Wen Nienhuys   |   address@hidden    | http://www.cs.uu.nl/~hanwen/