On 2014/10/31 22:50:35, Dan Eble wrote:
One thing just occurred to me. If this option is going into the UI,
do you
think the numbers should be 1-based for easier comprehension by
musicians? For
example, use '(1 . 9) to allow chording unisons to ninths, rather than
'(0 . 8)?
As a UI, numbers instead of intervals (possibly represented only by a pitch in relation to c' like \transposition does) do not make much sense. The sole motivation for numbers would be to make them distinguishable from music, and as we are piling options on, things will become increasingly awkward to tell apart by type since we are indeed talking about musical concepts all the time. Regarding such user interface extensions, I think we should rather go in the direction of <URL:https://code.google.com/p/lilypond/issues/detail?id=1321#c30>. Using context modifications makes it reasonably straightforward to add arbitrary named settings in arbitrary order on demand. I can rebase that patch if you want to see whether fitting a user interface there feels better. https://codereview.appspot.com/144170043/ _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
