Hi David(s, especially N) ;-)
2013/12/25 David Nalesnik :
> [tuplet problem]
> See attached. I apologize for any inconvenience.
It's great to see you working on C++ stuff! I'm sorry that i don't
have time to investigate this, but i'm rooting for you!
One piece of advice that i have: you may t
David Nalesnik writes:
> See attached. I apologize for any inconvenience.
>
> -David
> From 059ff4586a1e6a1fda27f40372a87db972be378c Mon Sep 17 00:00:00 2001
> From: David Nalesnik
> Date: Wed, 25 Dec 2013 09:41:39 -0600
> Subject: [PATCH] fix problem with connect-to-neighbor and break-overshoo
On Wed, Dec 25, 2013 at 12:58 PM, David Nalesnik
wrote:
> David,
>
> On Wed, Dec 25, 2013 at 12:56 PM, David Kastrup wrote:
>
> So even if you don't want to propose a "formal" commit, using "git diff"
>> in order to produce a properly readable patch that you can attach to a
>> mail will make peop
David,
On Wed, Dec 25, 2013 at 12:56 PM, David Kastrup wrote:
> David Nalesnik writes:
>
> >
> > I hesitate to submit a formal patch because I haven't worked with C++ in
> > LilyPond before,
>
> Formal or not, trying to figure out what you changed from just a quote
> of code is a major nuisance
David Nalesnik writes:
> In the "patch" below, I've suggested a modification of the relevant
> function in tuplet-bracket.cc which appears to fix the problem. (The
> replacement is above the commented-out section of the original.) You can
> see the results in the second image.
>
>
> I hesitate t
Hi again,
On Wed, Dec 25, 2013 at 12:41 PM, David Nalesnik
wrote:
>
>
> The following snippet demonstrates the problem (see attached image):
>
>
And here's the image of the default...
<>___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://list
Hi,
I just noticed something fishy about the interaction of
Tuplet.connect-to-neighbor and Tuplet.break-overshoot. The property
'break-overshoot is meant to apply to broken spanners, but here it is
having an effect on unbroken "connected" tuplet brackets. (Break-overshoot
is described as "How muc
