Re: Issue 1029 in lilypond: \thumb should behave like other fingerings

On 6/2/10 4:57 PM, "Xavier Scheuer" wrote: > Thank you Frédéric for the time you spend on this. > > > 2010/6/3 Carl Sorensen : > >> I think the answer to the other items is no. >> >> thumb is a Script grob, not its own grob.  Fingering is its own grob. >>  So I think you can't add all of the

Re: Issue 1029 in lilypond: \thumb should behave like other fingerings

Thank you Frédéric for the time you spend on this. 2010/6/3 Carl Sorensen : > I think the answer to the other items is no. > > thumb is a Script grob, not its own grob.  Fingering is its own grob. > So I think you can't add all of the grob properties to the script > alist.  All those other prop

Re: Issue 1029 in lilypond: \thumb should behave like other fingerings

On 6/2/10 3:35 PM, "Frédéric Bron" wrote: > If someone can help me on this, it would be nice. > Regards, Frédéric > > -- Forwarded message -- > Comment #3 on issue 1029 by frederic...@m4x.org: \thumb should behave > like other fingerings > http://code.google.com/p/lilypond/iss

Fwd: Issue 1029 in lilypond: \thumb should behave like other fingerings

If someone can help me on this, it would be nice. Regards, Frédéric -- Forwarded message -- Comment #3 on issue 1029 by frederic...@m4x.org: \thumb should behave like other fingerings http://code.google.com/p/lilypond/issues/detail?id=1029 So I would like to sum up all comments be

Re: different bar lines simultaneously?

Hi Arno, >> thanks! can one apply something like this also for just a small part >> of the whole piece? so that one can use normal behaviour in the rest >> of the score? I don't think so... once you've moved the bar and timing items, you've got to deal with it in each staff. However, if you put

Re: different bar lines simultaneously?

2010/6/2 Arno Waschk : > thanks! can one apply something like this also for just a small part > of the whole piece? so that one can use normal behaviour in the rest > of the score? > thanks again, arno That's a good question. I have not the answer, maybe someone else can help... Cheers, Xavier

Re: Calculations for spanner before its print function is called

Good deal! I used a callback - patch to be sent in the not-too-distant future. ~Mike On 6/2/10 4:26 PM, "Han-Wen Nienhuys" wrote: > On Wed, Jun 2, 2010 at 8:28 AM, Mike Solomon wrote: >>    I am toying around with a new spanner, and before it prints, I need to >> do some calculations on all o

Re: different bar lines simultaneously?

2010/6/2 Arno Waschk : > dear list, > > i am searching for a possibility to define different types of bar > lines in different staves simultaneously, in particular for defining > independent repeats for two instruments: > > / > |:m | m:|:m | m | m:| > |:m | m | m:|:m | m:| > \ > > m being some ran

different bar lines simultaneously?

dear list, i am searching for a possibility to define different types of bar lines in different staves simultaneously, in particular for defining independent repeats for two instruments: / |:m | m:|:m | m | m:| |:m | m | m:|:m | m:| \ m being some random music. i would not mind this being

Re: Calculations for spanner before its print function is called

On Wed, Jun 2, 2010 at 8:28 AM, Mike Solomon wrote: >    I am toying around with a new spanner, and before it prints, I need to > do some calculations on all of its broken_intos_.  I can easily do these > calculations in the print function by accessing the broken_into_ of > spanner->original (), b

LilyLib: error and warning as functions, program_name and _version as variables (issue1240042)

Looks good to me; it builds the docs from scratch. Please push. http://codereview.appspot.com/1240042/show ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Calculations for spanner before its print function is called

I tried setting a flag like that, but the problem is that the stencils are drawn in parallel and not in series, so by the time I've set this flag the other stencils are done doing their thing :-( ~Mike On 6/2/10 1:32 PM, "Carl Sorensen" wrote: > On 6/2/10 5:28 AM, "Mike Solomon" wrote: > >>

Re: Calculations for spanner before its print function is called

On 6/2/10 5:28 AM, "Mike Solomon" wrote: > Hey lilypond developers, > I am toying around with a new spanner, and before it prints, I need to > do some calculations on all of its broken_intos_. I can easily do these > calculations in the print function by accessing the broken_into_ of > spann

Calculations for spanner before its print function is called

Hey lilypond developers, I am toying around with a new spanner, and before it prints, I need to do some calculations on all of its broken_intos_. I can easily do these calculations in the print function by accessing the broken_into_ of spanner->original (), but then this calculation is done fo

Re: state of the release: the Good, the Bad, and the Ugly

> "Trevor" == Trevor Daniels writes: Trevor> David Kastrup wrote Wednesday, June 02, 2010 7:37 AM >> >> It is, for example, not possible to create your own dynamics >> commands with an audible result: the documentation on creating >> dynamics, including snippets, is silent on that if I am no

Re: Obstacles to LilyPond Development

Carl Sorensen writes: > On 6/1/10 1:26 AM, "David Kastrup" wrote: > >> Properties. There are tweaks, overrides, sets. Some of them work on >> some properties, and there is no user level coherence to what you >> need to do on what and why. Yes, I had some fits about that already, >> and some p

Re: state of the release: the Good, the Bad, and the Ugly

David Kastrup wrote Wednesday, June 02, 2010 7:37 AM I was talking about programming midi stuff. That there is enough material in the notation manual to get any output at all, and also to reassign midi instruments, I'll readily grant. But that's the minimum required to actually get midi at