lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Lilypond-auto] Issue 3140 in lilypond: Patch: Move Timing into separate


From: lilypond
Subject: [Lilypond-auto] Issue 3140 in lilypond: Patch: Move Timing into separate context
Date: Fri, 25 Jan 2013 16:27:33 +0000

Status: Started
Owner: address@hidden
Labels: Type-Enhancement Patch-new

New issue 3140 by address@hidden: Patch: Move Timing into separate context
http://code.google.com/p/lilypond/issues/detail?id=3140

Move Timing into separate context

The advantage over an alias at Score level is that setting Timing
variables before a Score context is established does not lead to error
messages.

Having a real, mostly ignored Timing context as a subcontext of Score
is a bit ugly, though.

An alternative would be to establish a Timing alias for Global instead
since Global is always present.  It would be somewhat unusual to
manipulate Global variables, however.

It can't be an alternative to actually _accept_ Timing at Global level
since get_score_context relies on Score being the only subcontext of
Global.

The last commit concerns just ly/engraver-init.ly and ly/performer-init.ly

There are two additional commits:


Make Timing_translator do a more thorough job of initializing Timing

Touches lily/timing-translator.cc


Replace base-fraction with base-length to simplify calculations

touches scm/define-music-callbacks.scm and scm/time-signature-settings.scm

http://codereview.appspot.com/7205057




reply via email to

[Prev in Thread] Current Thread [Next in Thread]