Hi David(s, especially N) ;-)
2013/12/25 David Nalesnik david.nales...@gmail.com:
[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
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 much
Hi again,
On Wed, Dec 25, 2013 at 12:41 PM, David Nalesnik
david.nales...@gmail.comwrote:
The following snippet demonstrates the problem (see attached image):
And here's the image of the default...
attachment: default-behavior.png___
David Nalesnik david.nales...@gmail.com 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.
David,
On Wed, Dec 25, 2013 at 12:56 PM, David Kastrup d...@gnu.org wrote:
David Nalesnik david.nales...@gmail.com 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
On Wed, Dec 25, 2013 at 12:58 PM, David Nalesnik
david.nales...@gmail.comwrote:
David,
On Wed, Dec 25, 2013 at 12:56 PM, David Kastrup d...@gnu.org 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
David Nalesnik david.nales...@gmail.com writes:
See attached. I apologize for any inconvenience.
-David
From 059ff4586a1e6a1fda27f40372a87db972be378c Mon Sep 17 00:00:00 2001
From: David Nalesnik david.nales...@gmail.com
Date: Wed, 25 Dec 2013 09:41:39 -0600
Subject: [PATCH] fix problem
