Re: Outside staff priority for tuplet bracket and tuplet number

[Trevor Daniels]

address@hidden wrote Monday, June 06, 2011 9:47 AM

> I am currently working off of a home-brewed branch 
> of LilyPond that places articulations on the inside 
> of tuplet numbers.  It uses the Pointer_group_interface 
> to make the tuplet bracket aware of scripts in 
> tuplet-engraver.cc and then factors the position of 
> these scripts into the vector `points' in 
> tuplet-bracket.cc (initialized in line 550).  However, 
> it seems like the collision-resolution should be 
> modifiable such that articulations can either be 
> placed above or below a TupletNumber / TupletBracket.  
> The same goes for any outside staff grob (markups, 
> dynamics, etc.) - it should be possible to place them 
> on the inside or on the outside of TupletBrackets.  
> I think this type of logic will help merge the tuplet 
> bracket and analysis bracket code.

Tuplet brackets should probably be recoded to work like
Slurs and the 'avoid-slur property.  Looks like quite a
bit of work though.

> Could all of this be cleared up if TupletBracket and 
> TupletNumber were redesigned to work as outside-staff 
> grobs?  Is there any disadvantage to doing this?

Making 'outside-staff-priority work properly for tuplets
would be a useful addition.  Probably easier than adding 
an 'avoid-tuplet property.

> Cheers,
> MS

Trevor