Re: Problem with scaled durations

2013-01-04 Thread Colin Hall
On Jan 4, 2013 10:51 PM, "Marek Klein" wrote: > > Hello, > > 2013/1/4 Colin Hall >> >> Oscar has run into a known issue with the limited precision of >> Rational in Lilypond. >> >> Although David is correct that this issue can crop up in many places >> it makes sense to follow Trevor's suggestion

Re: Enhancement request - lookup of sub-properties

2013-01-04 Thread Marek Klein
Hello, 2013/1/4 Nick Payne > See comment 13 of issue 3056: > http://code.google.com/p/lilypond/issues/detail?id=3056. At the moment, > when constructing an event function for a text spanner, one can't rely on > using ^ or _ to set the direction of the spanner if one wants to tweak > bound-detail

Re: Problem with scaled durations

2013-01-04 Thread Marek Klein
Hello, 2013/1/4 Colin Hall > Oscar has run into a known issue with the limited precision of > Rational in Lilypond. > > Although David is correct that this issue can crop up in many places > it makes sense to follow Trevor's suggestion and warn future users who > may end up with the same issue e

Enhancement request - lookup of sub-properties

2013-01-04 Thread Nick Payne
See comment 13 of issue 3056: http://code.google.com/p/lilypond/issues/detail?id=3056. At the moment, when constructing an event function for a text spanner, one can't rely on using ^ or _ to set the direction of the spanner if one wants to tweak bound-details.right.text according to the direct

Re: Fwd: Possible bug with minimumFret

2013-01-04 Thread David Kastrup
Federico Bruni writes: > 2013/1/4 Eluze > >> Yevgeny Lezhnin wrote >> > When I trying to change TabStaff.minimumFret to 3 there is 0 fret for >> > all notes, that can be on 0 fret. >> >> see the NR: >> >> http://www.lilypond.org/doc/v2.17/Documentation/notation/common-notation-for-fretted-string

Re: Fwd: Possible bug with minimumFret

2013-01-04 Thread Colin Hall
On Fri, Jan 04, 2013 at 12:34:08PM +0100, Federico Bruni wrote: > 2013/1/4 Eluze > > > Yevgeny Lezhnin wrote > > > When I trying to change TabStaff.minimumFret to 3 there is 0 fret for > > > all notes, that can be on 0 fret. > > > > see the NR: > > > > http://www.lilypond.org/doc/v2.17/Documentat

Re: Problem with scaled durations

2013-01-04 Thread Colin Hall
On Fri, Jan 04, 2013 at 10:22:02AM -, Trevor Daniels wrote: > > David Kastrup wrote Friday, January 04, 2013 9:15 AM > > > "Trevor Daniels" writes: > > > >> David Kastrup wrote Friday, January 04, 2013 8:21 AM > >> > >>> Oscar Dub writes: > > From a user perspective, I thought it

Re: Fwd: Possible bug with minimumFret

2013-01-04 Thread Federico Bruni
2013/1/4 Eluze > Yevgeny Lezhnin wrote > > When I trying to change TabStaff.minimumFret to 3 there is 0 fret for > > all notes, that can be on 0 fret. > > see the NR: > > http://www.lilypond.org/doc/v2.17/Documentation/notation/common-notation-for-fretted-strings > > Even when minimumFret is set,

Re: Problem with scaled durations

2013-01-04 Thread Trevor Daniels
David Kastrup wrote Friday, January 04, 2013 9:15 AM > "Trevor Daniels" writes: > >> David Kastrup wrote Friday, January 04, 2013 8:21 AM >> >>> Oscar Dub writes: From a user perspective, I thought it might be nice for the compiler to send out some kind of error or warning messa

Re: Fwd: Possible bug with minimumFret

2013-01-04 Thread Eluze
Yevgeny Lezhnin wrote > When I trying to change TabStaff.minimumFret to 3 there is 0 fret for > all notes, that can be on 0 fret. see the NR: http://www.lilypond.org/doc/v2.17/Documentation/notation/common-notation-for-fretted-strings Even when minimumFret is set, open strings are used whenever

Re: Problem with scaled durations

2013-01-04 Thread David Kastrup
"Trevor Daniels" writes: > David Kastrup wrote Friday, January 04, 2013 8:21 AM > >> Oscar Dub writes: >>> >>> From a user perspective, I thought it might be nice for the compiler >>> to send out some kind of error or warning message. Currently there's >>> no sign of anything wrong except the fi

Re: Problem with scaled durations

2013-01-04 Thread Trevor Daniels
David Kastrup wrote Friday, January 04, 2013 8:21 AM > Oscar Dub writes: >> >> From a user perspective, I thought it might be nice for the compiler >> to send out some kind of error or warning message. Currently there's >> no sign of anything wrong except the final output. Is this valid >> enoug