[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-devel
Subject:    Re: make metronomeMarkFormatter more flexible (issue 327620043 by lilypond@maltemeyn.de)
From:       lilypond () maltemeyn ! de
Date:       2017-10-30 15:20:07
Message-ID: 001a1141efe2765948055cc52cf9 () google ! com
[Download RAW message or body]

On 2017/10/30 07:44:49, Malte Meyn wrote:
> Apart from that I posted a code at
> https://sourceforge.net/p/testlilyissues/issues/5215/#505b that tries
to go into
> the direction of Kieren's latest suggestion.

This approach would work if it didn't have to collect all needed
information from grob, context and event properties but only from grob
properties. Currently, the grob property 'text is set by the
metronomeMarkFormatter which takes input from event (f. e. 'text) and
context (f. e. 'tempoHideNote) properties.

Ok, technically, it's possible to get the other properties (as one can
see at the bottom of that code example, but that would be really
confusing (I don't know a better word for the German "unübersichtlich").

https://codereview.appspot.com/327620043/
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

[prev in list] [next in list] [prev in thread] [next in thread]