Inconsistency with Staves y coordinates

[ldupoueyUB]

Hi !
I'm rendering scores as described here : https://alphatab.net/docs/guides/lowlevel-apis#rendering-files-via-scorerenderer.
My goal is to know the Y positions of the rendered staves. My first approach was to accumulate the heights of the svgChunks to compute the Y coordinate of next chunk (and next staff).
That worked pretty well but I though it might be cleaner to use the BoundsLookup attribute of the staffSystems. Doing so works great for X coordinates but when it come to Y I have a 40ish pixels offset compared to first approch that doesnt seem to correspond to anything. Any idea where it could come from ?
Léo

[Danielku15]

TBH, the samples are slightly outdated. The chunks you receive in partialRenderFinished are absolutely positioned and you also get an x/y coordinate where to position them.

Here is a more up-to-date example (from the Node.js PNG rendering guide). but the positioning part applies to SVGs too.
https://alphatab.net/docs/guides/nodejs#combine-all-individual-pngs-into-one-final-one-and-save-it

But in the end it depends on what you are exactly doing. Maybe you can prepare a small fiddle showing your problem.

[ldupoueyUB]

Thank you very much, the example provided makes everything clearer. The issue came from alphatab default padding (alphatabSettings.display.padding) but using renderResult.x and renderResult.y allow to take the padding into account smoothly.
Léo