Re: [Lilypond-auto] Issue 4449 in lilypond: Stacked tuplets crash

[lilypond]

Comment #6 on issue 4449 by address@hidden: Stacked tuplets crash
https://code.google.com/p/lilypond/issues/detail?id=4449

With the release of 2.19.21, existing code that sets the TupletNumber to #f  
for a nested tuplet causes the reported core dump. If instead one sets the  
TupletNubmer stencil to #point-stencil, code compiles fine.

Clearly a change has occurred with 2.19.21. The workaround is to use  
#point-stencil and not #f. This makes sense considering the dimensions of  
the number object are used for correct processing in relation to the  
containing tuplet, but it would be better if using #f did not crash  
lilypond, but issues a warning or even fatal error messages instead.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings