bug-lilypond
[Top][All Lists]
Advanced

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

Re: Issue 2047 in lilypond: Patch: Add \accidentalStyle command


From: address@hidden
Subject: Re: Issue 2047 in lilypond: Patch: Add \accidentalStyle command
Date: Wed, 23 Nov 2011 09:15:03 +0100

On Nov 23, 2011, at 8:09 AM, address@hidden wrote:

> 
> Comment #9 on issue 2047 by address@hidden: Patch: Add \accidentalStyle 
> command
> http://code.google.com/p/lilypond/issues/detail?id=2047
> 
> Tsk tsk tsk.  Currently working on the documention, and it is rather stupid 
> that we have \accidentalStyle "default" but $(set-accidental-style "default" 
> 'GrandStaff).  I lean towards allowing _only_ strings as accidentalStyle 
> (currently accidentalStyle #'default is working) and instead take an optional 
> symbol argument, like
> \accidentalStyle #'GrandStaff "default".  At the time the command is 
> executed, I can't use ly:context-find for reliably distinguishing context 
> symbols from others.
> 
> When I manage getting assignments into arguments, \accidentalStyle GrandStaff 
> = #'default would be nice, but I don't yet have a good workable plan for that.
> 
> People ok with reserving symbols for context specification, allowing only 
> strings for style spec?

I'm the last person to have the right to make any claims about how to do UI 
but, that said, here I go.  Currently, all style-related properties are symbols 
(Flag #'style, etc.).  Insofar as this is a context modification, I realize 
that the syntax has to be different, but it may be strange to users to remember 
this one exception.

Unfortunately, I can't think of a good workaround, but I figured I'd raise that 
issue.

Cheers,
MS


reply via email to

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