Updates:
Status: Verified
Comment #10 on issue 569 by v.villenave: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
The convert rules look fine to me, so I'm marking this as Verified. Thanks!
--
You received this message because you
Comment #9 on issue 569 by Carl.D.Sorensen: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Frederic and Neil,
I'm taking care of this right now. I'm using this as an opportunity to
test the CG instructions for running convert-
ly on t
Comment #8 on issue 569 by n.puttock: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
No problem, you've done a fine job where it matters; these old overrides
don't break
anything critical (apart from the aesthetics of the snippets, of co
Comment #7 on issue 569 by frederic...@m4x.org: Consistency in property
names: beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Sorry for that. As soon as the tests passed I though it was OK. Can you
give me some
directions on where are the files I have to change? Then
Comment #6 on issue 569 by n.puttock: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Frédéric, the convert rule is for the wrong version (2.13.1). I've moved
it to the
end of the rules for 2.13.4 and added a description.
There are sti
Updates:
Status: Fixed
Labels: fixed_2_13_4
Comment #5 on issue 569 by Carl.D.Sorensen: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Oops -- sorry for doing it wrong. I think it's right now
--
You received this message
Updates:
Status: fixed_2_13_4
Comment #4 on issue 569 by Carl.D.Sorensen: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Thanks to Frederic for his work!
--
You received this message because you are listed in the owner
or CC field
Updates:
Owner: Carl.D.Sorensen
Comment #3 on issue 569 by Carl.D.Sorensen: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
Updates:
Status: Started
Comment #2 on issue 569 by Carl.D.Sorensen: Consistency in property names:
beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Assigned to Frederic Bron as a Frog task.
--
You received this message because you are listed in the owner
or CC f
2008/2/7, Mats Bengtsson <[EMAIL PROTECTED]>:
> > Issue 569: Consistency in property names: beam-thickness
> > http://code.google.com/p/lilypond/issues/detail?id=569
> >
> > Comment #1 by hanwenn:
> > I prefer to go for beam-thickness ; I think doc strings with
> > exceptions and
> > properties wit
[EMAIL PROTECTED] wrote:
Issue 569: Consistency in property names: beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Comment #1 by hanwenn:
I prefer to go for beam-thickness ; I think doc strings with
exceptions and
properties with different 'types' are messy
Fine with m
Issue 569: Consistency in property names: beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
Comment #1 by hanwenn:
I prefer to go for beam-thickness ; I think doc strings with exceptions and
properties with different 'types' are messy
--
You received this message because
On the other hand, if we do this change, then we loose the consistency with
all other objects, where the property name "thickness" is used to denote
the thickness. In my opinion, we would get even more consistency if we
renamed beam-thickness to thickness also for StemTremolo objects
(even though,
Issue 569: Consistency in property names: beam-thickness
http://code.google.com/p/lilypond/issues/detail?id=569
New issue report by v.villenave:
Currently, the beam-thickness property is only used for
StemTremolo objects. It might be better to change
the property name for the thickness of all bea
14 matches
Mail list logo
