Re: Distance of a grob from its reference point

[Paolo Prete]

In other words, this means: "if you are lucky enough that the position estimated by Lilypond is the same that you have in mind, offset will offset to the quantity that you want. Otherwise it will led to improper placement (because it will mix the value that it has in mind, with the value that you have in mind)". Given that you obviously don't know what Lilypond estimates (and Lilypond doesn't know as well what you estimates) this ends in forcing the user to make improper trial and error procedures, with random values. 

Again: please, correct me if I am wrong. I would be *really* happy to find a way to use this properties. They are essential for the automatic avoid-collision algos.  

On Wed, Jan 15, 2020 at 10:57 PM Paolo Prete <address@hidden> wrote:

I quote Carl's words:

"So offset applies to the *estimated* position, and then the spacing engine works on the offset+estimated postion and ends up putting things where it thinks they belong"

I checked that with the examples made before and it seems absolutely true.

Then: you have to offset an estimated position. How could you do that if you don't know this estimated position?

Best,

P

On Wed, Jan 15, 2020 at 10:46 PM Aaron Hill <address@hidden> wrote:

On 2020-01-15 1:21 pm, Paolo Prete wrote:
> Without a proper behavior of the "\offset" command you cannot do nor
> the
> automatic 2) placement, nor a fine tuning.

What is "proper behavior" for \offset to you?  It is my understanding
\offset works precisely as documented, but that is a worthless metric if
the documented behavior is not what people need of a tool.


-- Aaron Hill