[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Determining what parameters exist for an item
From: |
Thomas Morley |
Subject: |
Re: Determining what parameters exist for an item |
Date: |
Sun, 24 Jan 2016 22:22:35 +0100 |
2016-01-24 22:03 GMT+01:00 Kieren MacMillan <address@hidden>:
> Hi Harm,
>
>> Well, it is the _actual_ default. KeyCancellation _can't_ have
>> a general default of X-extent for all possible KeyCancellations…
>
> Obviously. =)
>
> But the benefits of the function are both general (“Get a list of every
> settable property for this grob.”)
But please understand: if a property is settable, this does not mean
your setting takes any effect.
I don't speak of user-errors in syntax, missing context, etc, but
sometimes an engraver does not listen to a certain property, maybe
because it's hard-coded or not really needed or for other good
reasons.
Btw, I tested it with 2.18.2, doesn't work with \applyOutput, but with
\override Grob.after-line-breaking
Cheers,
Harm
> and specific (“Get the property values for a particular instance of this
> grob.”) I suppose we could spoonfeed the user more by somehow
> highlighting/mentioning in the output which are general/fixed values and
> which are specific/instance/relative values… but having this function already
> puts us well ahead of where we were a few hours ago.
>
>> Well, we have the \offset-function ...
>> No clue about possible limitations, though
>
> The \offset function behaves in a “user-inconsistent” manner — by which I
> mean, there is undoubtedly a perfectly logical/technical reason why it works
> in certain cases and throws errors in others, but users don’t (or at least
> shouldn’t) care why they see “inconsistent” [sic] behaviour.
>
> Simon says:
>> Oh, it would be great if we could use \offset for such cases.
>
>
> +1
> But I know it may not be possible.
>
> One case where a lack of \offset-ability drives me crazy is explicit
> system/staff positioning: as far as I know (and queries to the list have
> confirmed), there is no way to “nudge” a system (e.g.) up 1 staff space. So
> there’s a lot of trial-and-error in those situations.
>
> Best,
> Kieren.
> ________________________________
>
> Kieren MacMillan, composer
> ‣ website: www.kierenmacmillan.info
> ‣ email: address@hidden
>
- Re: Determining what parameters exist for an item, (continued)
- Re: Determining what parameters exist for an item, Kieren MacMillan, 2016/01/24
- Re: Determining what parameters exist for an item, Thomas Morley, 2016/01/24
- Re: Determining what parameters exist for an item, Simon Albrecht, 2016/01/24
- Re: Determining what parameters exist for an item, Simon Albrecht, 2016/01/24
- Re: Determining what parameters exist for an item, Thomas Morley, 2016/01/24
- Re: Determining what parameters exist for an item, David Nalesnik, 2016/01/24
- Re: Determining what parameters exist for an item, Simon Albrecht, 2016/01/25
- Re: Determining what parameters exist for an item, David Kastrup, 2016/01/25
- Re: Determining what parameters exist for an item, Simon Albrecht, 2016/01/25
- Re: Determining what parameters exist for an item, Kieren MacMillan, 2016/01/24
- Re: Determining what parameters exist for an item,
Thomas Morley <=
- Re: Determining what parameters exist for an item, Thomas Morley, 2016/01/24
- Re: Determining what parameters exist for an item, Kieren MacMillan, 2016/01/25
- Re: Determining what parameters exist for an item, David Nalesnik, 2016/01/25
- Re: Determining what parameters exist for an item, Thomas Morley, 2016/01/25
- Re: Determining what parameters exist for an item, Thomas Morley, 2016/01/24
- RE: Determining what parameters exist for an item, Charles O. Lawrence, 2016/01/24
RE: Determining what parameters exist for an item, Charles O. Lawrence, 2016/01/23
Re: Determining what parameters exist for an item, Charles O. Lawrence, 2016/01/23