Re: Some things need need to be fixed on the interfaces pages

2024-12-13 Thread Werner LEMBERG
>> I'm left-handed by myself (but playing the piano), and I don't feel >> offended 🙂 > > But aren't you playing a right-handed piano? I do. However, I'm not *completely* left-handed – AFAIK, completely left-handed people are quite rare. For example, while I write with my left hand or hold a sp

Re: Some things need need to be fixed on the interfaces pages

2024-12-13 Thread Jeff Olson
On 12/13/2024 12:38 AM, Werner LEMBERG wrote: 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 🙂 But aren't you playing a right-handed piano? (My guitar instructor uses that as ev

Re: Some things need need to be fixed on the interfaces pages

2024-12-12 Thread Werner LEMBERG
> *If* we had a page that showed all grob properties, then we could do > that. My bad, we actually have that :-) So yes, your suggestion is sound, and the list of grob properties could be amended accordingly. Werner

Re: Some things need need to be fixed on the interfaces pages

2024-12-12 Thread Werner LEMBERG
>>> 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,

Re: Some things need need to be fixed on the interfaces pages

2024-12-12 Thread Christopher Heckman
On Thu, Dec 12, 2024 at 4:05 PM David Kastrup wrote: > > Christopher Heckman writes: > > > On Wed, Dec 11, 2024 at 10:58 PM Werner LEMBERG wrote: > >> > >> >> IIRC, a suggestion in the mentioned thread is to make the property > >> >> description displayed for a given grob show which interfaces i

Re: Some things need need to be fixed on the interfaces pages

2024-12-12 Thread David Kastrup
Christopher Heckman writes: > On Wed, Dec 11, 2024 at 10:58 PM Werner LEMBERG wrote: >> >> >> IIRC, a suggestion in the mentioned thread is to make the property >> >> description displayed for a given grob show which interfaces it is >> >> part of, for example >> >> >> >> ``` >> >> ‘spacing-pair

Re: Some things need need to be fixed on the interfaces pages

2024-12-12 Thread Christopher Heckman
On Wed, Dec 11, 2024 at 10:58 PM Werner LEMBERG wrote: > > >> IIRC, a suggestion in the mentioned thread is to make the property > >> description displayed for a given grob show which interfaces it is > >> part of, for example > >> > >> ``` > >> ‘spacing-pair’ (pair) > >> interface(s): > >>

Re: Some things need need to be fixed on the interfaces pages

2024-12-11 Thread Werner LEMBERG
> I mean should MMRs actually use centered-spanner-interface? MMRs are > after all spanners that are centered between spacing-pair. It looks > to me like the C++ code for MMRs does exactly the same offset > calculation as centered-spanner-interface::calc-x-offset, though not > all in one place.

Re: Some things need need to be fixed on the interfaces pages

2024-12-11 Thread Werner LEMBERG
>> Exactly this is not possible, because there exists only a single, >> global property called `spacing-pair`, which consequently has a >> single, global description. >> >> In other words, the auto-generated documentation sees that an >> interface uses `spacing-pair`, and it shows its description.

Re: Some things need need to be fixed on the interfaces pages

2024-12-11 Thread Werner LEMBERG
>> IIRC, a suggestion in the mentioned thread > > Do you know the name of that thread? I tried searching for it, but > couldn't come up with anything. It's mentioned at the top of https://gitlab.com/lilypond/lilypond/-/issues/6210 namely https://lists.gnu.org/archive/html/lilypond-user/2

Re: Some things need need to be fixed on the interfaces pages

2024-12-11 Thread Christopher Heckman
On Tue, Dec 10, 2024 at 9:38 PM Werner LEMBERG wrote: > > >> The policy of LilyPond is to avoid different property names for > >> similar functionality, which often leads to cryptic property > >> descriptions to be as generic as possible. In this particular case > >> an example is given, which is

Re: Some things need need to be fixed on the interfaces pages

2024-12-11 Thread Christopher Heckman
On Tue, Dec 10, 2024 at 9:38 PM Werner LEMBERG wrote: > > >> The policy of LilyPond is to avoid different property names for > >> similar functionality, which often leads to cryptic property > >> descriptions to be as generic as possible. In this particular case > >> an example is given, which is

Re: Some things need need to be fixed on the interfaces pages

2024-12-11 Thread Saul Tobin
I mean should MMRs actually use centered-spanner-interface? MMRs are after all spanners that are centered between spacing-pair. It looks to me like the C++ code for MMRs does exactly the same offset calculation as centered-spanner-interface::calc-x-offset, though not all in one place. On Tue, Dec

Re: Some things need need to be fixed on the interfaces pages

2024-12-10 Thread Werner LEMBERG
>> The policy of LilyPond is to avoid different property names for >> similar functionality, which often leads to cryptic property >> descriptions to be as generic as possible. In this particular case >> an example is given, which is actually a good thing, but it doesn't >> cover the `centered-sp

Re: Some things need need to be fixed on the interfaces pages

2024-12-10 Thread Christopher Heckman
On Tue, Dec 10, 2024 at 12:58 AM Werner LEMBERG wrote: > > > I went through the interfaces pages recently, and I found a couple of > > things that need to be fixed (these is from the 2.25 version). > > > > (1) The centered-spanner-interface page talks about using it with > > MultiMeasureRest,

Re: Some things need need to be fixed on the interfaces pages

2024-12-09 Thread Werner LEMBERG
> I went through the interfaces pages recently, and I found a couple of > things that need to be fixed (these is from the 2.25 version). > > (1) The centered-spanner-interface page talks about using it with > MultiMeasureRest, but MultiMeasureRest isn't among the list of > grobs at the b