Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-06 Thread Valentin Villenave
2008/10/6 Reinhold Kainhofer <[EMAIL PROTECTED]>: > Okay, applied. I've also closed that issue at Rietveld. Can someone with > access also close Lilypond's issue #691? Hi Reinhold, it works well... but the parentheses are still printed, even without a note inside. So that makes tempo indication

Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-06 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 6. Oktober 2008 schrieb Neil Puttock: > 2008/10/6 Reinhold Kainhofer <[EMAIL PROTECTED]>: > > Patch can be found at: > > http://codereview.appspot.com/6672 > > > > Please review. > > LGTM. Okay, applied. I've also closed that issue at Rietv

Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-06 Thread Neil Puttock
2008/10/6 Reinhold Kainhofer <[EMAIL PROTECTED]>: > Patch can be found at: > http://codereview.appspot.com/6672 > > Please review. LGTM. I'd be surprised if unsetting both properties caused any problems. BTW, can I point you gently in the direction of this thread: http://lists.gnu.org/archive/h

Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-06 Thread Valentin Villenave
2008/10/6 Reinhold Kainhofer <[EMAIL PROTECTED]>: > Patch can be found at: > http://codereview.appspot.com/6672 Arrr, you're fast! I precisely wanted to take this as a chance to get more familiar with the C++ code... I had found the location, but I was still missing the make-property-unset functi

Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-06 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 6. Oktober 2008 schrieb Valentin Villenave: > 2008/10/1 Valentin Villenave <[EMAIL PROTECTED]>: > > Yes!! For a few weeks I wanted to submit exactly the same feature > > request, but you made it first (and much better than I would have). > >

Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-06 Thread Valentin Villenave
2008/10/1 Valentin Villenave <[EMAIL PROTECTED]>: > Yes!! For a few weeks I wanted to submit exactly the same feature > request, but you made it first (and much better than I would have). Hi Thies, your report has been added as http://code.google.com/p/lilypond/issues/detail?id=691 Cheers, Valent

Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-01 Thread Alexander Kobel
Valentin Villenave wrote: > [...] > The ultimate enhancement would be that when you type \tempo "Andante" > LilyPond would recognize it and attribute a default Andante tempo to > the MIDI rendering... but maybe that's science-fiction. > [...] I guess this would neither be necessary nor good. There

Re: Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-01 Thread Valentin Villenave
2008/10/1 Thies Albrecht <[EMAIL PROTECTED]>: > Once a tempo indication dur = count is explicitly set, it will be displayed > even though you just indicate e.g. \tempo "Allegro". A simple workaround > would be to use \once \set Score.tempoHideNote = ##t everytime you just want > the textual tem

Tempo mark doesn't forget explicitly given bpm, v. 2.11.60

2008-10-01 Thread Thies Albrecht
> I'm not top posting Hi everybody! Using the new tempo mark function I get the following bug: Once a tempo indication dur = count is explicitly set, it will be displayed even though you just indicate e.g. \tempo "Allegro". A simple workaround would be to use \once \set Score.tempoHideNote = ##