Re: How to increase the distance between the last note of a measure and the following bar line

[Jean Abou Samra]

[Kieren]
> > The page in the Internals Reference doesn't
> > list all the properties that the grob would
> > support, only those for which it has a specific
> > default. You have to explore the interfaces to
> > find other interesting properties that you can
> > tweak. In this case, click "Item" ("This object
> > is of class Item"). You'll find extra-spacing-width
> > in the item-interface.
> This is something I’ve asked a couple times before, but been dismissed… Maybe 
> you can help?
>
> Is there an Automagic™ way to print out a “complete tree” of all properties 
> that a grob supports, including any default values?


Sure. How about the attached?

Bear in mind that this may stop working in future
versions (in fact I have a branch somewhere that
would definitely break it if I ever manage to
complete the work).


[Paolo]
> Thanks.
>
> However, when looking for a property or function that might fit what I 
> need, I always check for inherited stuff. In this case, unfortunately, 
> the search is a bit cumbersome and tricky and it's not the first time, 
> especially when the properties are so many and I have to write the 
> code quickly, that I don't find the right property.
> Suppose that an object has many settable properties: there is a main 
> page of this object, let's call it "A", and other pages with inherited 
> properties (B, C, D, E etc.)
> When I do a search, I first look inside A: if I don't find anything 
> useful, I look in B and if I don't find anything useful here too, I go 
> back to A and then I go to C etc.
> You can understand that, when there are so many properties, jumping 
> back and forth from page to page is inconvenient to remember what is 
> available as a sum of things. In many automatic documentation of other 
> libraries I use, the inherited properties and functions are listed 
> grouped (with relative links), sometimes in small format, at the 
> bottom of the page to avoid this inconvenience.
> It is true that the resulting page is longer, but it is not heavier to 
> read. Furthermore, in this way you can read only the names, without 
> the descriptions, of these properties and this allows you to decide 
> whether or not to jump to the page that defines the inherited property 
> to try. Mine is a suggestion, and I think it's useful to add it to the 
> documentation (or at least explain how to create this "extra" 
> documentation automatically)


Would the attached mock a good way to format
this documentation in your opinion?

Best,
Jean

ir-grob-formatting.ly
Description: Text Data