On Thu, Jun 23, 2016 at 2:55 AM, Thomas Morley-2 [via Lilypond] < [email protected]> wrote:
> X-offset and Y-offset are working more like 'extra-offset. > They do, but extra-offset is based on the default X-offset and Y-offset values. Setting Y-offset here is based on the page's zero-reference (the bottom of the top allowable location). Likewise for X-offset (from the left-side). So, why not make Y-offset behave like it does for every other grob (i.e., it influences the vertical spacing of other staves/systems around it) and add the extra-offset property such that it behaves like it does for every other grob (i.e., it moves the staff/system, but doesn't influence the spacing of any other staff/system)? Another idea. What if, when calculating the vertical-skyline, setting the Y-offset value could vertically offset the skyline up or down making the system/staff seem bigger or smaller to the spacing algorithms than it actually is? I guess that's more like changing Y-extent, but maybe there could be a convenient way to do that? 'extra-Y-extent maybe? It could take a pair where the car is the lower side and the cdr is the upper side? Just some thoughts. I think it's desireable to get (at least some of) the old > possibilities working again, so that the interplay of manually > tweaking the automatic behaviour works nicely. > No idea how hard it would be to reimplement this, though. > +1! Best, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/What-to-do-with-input-regression-page-spacing-ly-tp191822p191860.html Sent from the Dev mailing list archive at Nabble.com. _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
