On 8/21/2015 4:14 PM, David Nalesnik-2 [via Lilypond] wrote:
> Hi,
>
> On Fri, Aug 21, 2015 at 2:37 PM, David Kastrup <[hidden email]
> </user/SendEmail.jtp?type=node&node=179907&i=0>> wrote:
>
> tisimst <[hidden email]
> </user/SendEmail.jtp?type=node&node=179907&i=1>> writes:
>
> > On 8/21/2015 5:40 AM, Andrew Bernard [via Lilypond] wrote:
> There was one oddity I encountered in the process, though. When I
> > irregularized the flags, I noticed that a flag is printed for
> EVERY note
> > within the same chord! Crazy, I know. Sounds like an unnecessary
> thing
> > if you ask me.
>
> Sounds like an undiscovered bug if you ask me.
>
>
> Yes, I think so.
>
> It appears that there is no provision for redundant flags in Flag::print.
>
> The attached is a diff for a quick test fix. Only one of the flags is
> actually pointed to by Stem.flag, and we keep it, suiciding the
> others. Don't know if that's adequate.
>
> You can compare the results with and without using this:
Now that's good customer service :-) I'd like to see ANY tech company
fix a customer-reported bug that fast. Thanks David!
- Abraham
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/instrument-name-or-markup-question-tp46635p179908.html
Sent from the User mailing list archive at Nabble.com.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
