Looks great.
You can simplify the version in changes. The two tuplets sharing share
one beam catches the eye, but that was not the change. I wrote a
version below imagining a reader who has forgotten that the fraction in
\times is backwards, and didn't yet notice that LilyPond commands can
have
bwwtolilly is a typo, isn't it?
(diff view doesn't work for some reason.)
https://codereview.appspot.com/7098055/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 28 janv. 2013, at 06:33, Keith OHara wrote:
> On Sun, 27 Jan 2013 01:45:16 -0800, m...@mikesolomon.org
> wrote:
>
>> On 26 janv. 2013, at 23:21, k-ohara5...@oco.net wrote:
>>
>>> The tracker says the overall goal is to remove a call to the function
>>> translate_axis. In the example
>>>
People can review this if they have time...it is a lot of code, but it
is more a progress report than anything else.
To resume a bit of what's been said before: once translate_axis is
called, the dim_cache of grobs is set and it is very difficult to work
with approximations. This makes cross-sta
