[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Some things need need to be fixed on the interfaces pages
From: |
Werner LEMBERG |
Subject: |
Re: Some things need need to be fixed on the interfaces pages |
Date: |
Fri, 13 Dec 2024 07:38:14 +0000 (UTC) |
>>> There's a problem there, too, in that the default value depends on
>>> the grob.
>>>
>>> In MeasureSpanner, the default value is (staff-bar . staff-bar)
>>>
>>> In PercentRepeat, it's (break-alignment . staff-bar)
>>
>> I don't see a problem here.
>
> You can't talk about *the* default value, because it's not unique;
> you can only talk about *a* default value.
The improved version of a grob description I showed neither uses a
definite nor an indefinite article for that. I think it should be
clear that on a page that describes grob 'foo', the displayed default
value is for exactly this grob. Don't you agree?
>> Maybe a grob description on the page showing the available default
>> properties for `MeasureSpanner` could be displayed [...]
>
> The default values seem to be set in grobs, not interfaces, so as an
> alternative, how about something like ...
>
> ‘spacing-pair’ (pair)
> A pair of alignment symbols which set an object's spacing
> relative to its left and right ‘BreakAlignment’s.
>
> interface(s):
> centered-spanner-interface, multi-measure-interface
> default value in grob(s):
> CenteredBarNumber: [none]
> MeasureCounter: '(break-alignment . break-alignment)
> MultiMeasureRest: '(break-alignment . break-alignment)
> PercentRepeat: '(break-alignment . staff-bar)
>
> (with the appropriate links added)
*If* we had a page that showed all grob properties, then we could do
that. However, right now we repeat a property description for each
and every grob if it gets used. Assuming a description page for grob
'foo' I see no additional value in having default values displayed for
other grobs; this just makes the description unnecessarily longer.
>> A user can also very easily define new commands that better fits
>> the intended purpose, for example,
>>
>> ```
>> strummingHandFinger = \rightHandFinger
>> ```
>
> Yes. Also, I guess not as many left-handed players are upset about
> this as I thought.
I'm left-handed by myself (but playing the piano), and I don't feel
offended :-) By the way, AFAIK you are the very first person that ever
mentioned this issue.
Werner
- Re: Some things need need to be fixed on the interfaces pages, (continued)
- Re: Some things need need to be fixed on the interfaces pages, Werner LEMBERG, 2024/12/10
- Re: Some things need need to be fixed on the interfaces pages, Christopher Heckman, 2024/12/10
- Re: Some things need need to be fixed on the interfaces pages, Christopher Heckman, 2024/12/11
- Re: Some things need need to be fixed on the interfaces pages, Werner LEMBERG, 2024/12/12
- Re: Some things need need to be fixed on the interfaces pages, Christopher Heckman, 2024/12/12
- Re: Some things need need to be fixed on the interfaces pages, David Kastrup, 2024/12/12
- Re: Some things need need to be fixed on the interfaces pages, Christopher Heckman, 2024/12/12
- Re: Some things need need to be fixed on the interfaces pages,
Werner LEMBERG <=
- Re: Some things need need to be fixed on the interfaces pages, Werner LEMBERG, 2024/12/13
- Re: Some things need need to be fixed on the interfaces pages, Jeff Olson, 2024/12/13
- Re: Some things need need to be fixed on the interfaces pages, Werner LEMBERG, 2024/12/13
- Re: Some things need need to be fixed on the interfaces pages, Christopher Heckman, 2024/12/11
- Re: Some things need need to be fixed on the interfaces pages, Werner LEMBERG, 2024/12/12