|
From: | Simon Albrecht |
Subject: | Re: Determining what parameters exist for an item |
Date: | Sun, 24 Jan 2016 21:32:01 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
On 24.01.2016 21:28, Simon Albrecht wrote:
On 24.01.2016 21:15, Thomas Morley wrote:Now, if I want to reduce or enlarge KeyCancellation.X-extent, knowing that default is (0.0 . 5.866662)*** gives me critical information that I can actually use as a reference point; without that information, the trial-and-error factor increases dramatically.Well, we have the \offset-function ... No clue about possible limitations, thoughOh, it would be great if we could use \offset for such cases. Unfortunately it doesn’t work here… David, is this the case you described in <http://sourceforge.net/p/testlilyissues/issues/4516/#1cc7>, with mutable properties?
Test case: %%%%%%%%%%% \version "2.19.35" { \key fis \major 1 \once\override Staff.KeyCancellation.X-extent = #'(0 . 5) \key b \minor 1 \once\offset X-extent #'(0 . 5) Staff.KeyCancellation \key g \major 1 } %%%%%%%%%%– throwing twice ‘warning: the property 'X-extent of #<Grob KeyCancellation > cannot be offset’ and printing the KeyCancellation _without_ any X-extent.
Yours, Simon
[Prev in Thread] | Current Thread | [Next in Thread] |