Re: flag position problems with flat-flag style

Gilberto Agostinho wrote > I noticed that the length of the stems in beamed > notes changed considerably after I used your suggestion below, they are > now > much taller than before: Hi Gilberto, Oh, bummer, I had forgotten to set some values back to default after playing around with them...

Re: flag position problems with flat-flag style

Gilberto Agostinho wrote > Wouldn't it be possible to add a conditional to check for those? If an > user > uses flat-flag then they certainly would also prefer these stem length > settings that you posted. Having this automatized would be great. Hmmm, At first glance, that seems to be a good

Re: flag position problems with flat-flag style

Torsten Hämmerle writes: > Any automatic interference (even if it's only in a special case like for > flat-flag-style) could lead to unpredictable results and the user would lose > part of the freedom and flexibility to set any desired value by modifying > the details

Re: flag position problems with flat-flag style

Hi all, Thanks for all your replies. David Kastrup wrote > You don't _need_ to override the whole list. You could just override > single properties from it. You are of course right, David, I can just use: \override Stem.details.lengths = #'(3.5 3.5 3.5 4.5 5.0 6.0) Thanks for the tip.

Re: Collision of Fingering and DotColumn

Thomas Morley-2 wrote > Seems to be triggered by the second, but only if the left note is on a > line. Hi Harm, It's definitively the dots being forced down. When applying \override Dots #'staff-position = #-1 the fingering misplacement will also occur in all the other cases. Interestingly

Collision of Fingering and DotColumn

Hi, the code below produces a collision of Fingering and DotColumn in certain cases. \version "2.19.81" mus = { \set fingeringOrientations = #'(right) 4... } { \cadenzaOn \mus \transpose c d \mus \transpose c e \mus \transpose c f \mus \transpose c g \mus