David Nalesnik wrote Saturday, November 01, 2014 11:53 PM > On Sat, Nov 1, 2014 at 6:21 PM, Trevor Daniels <[email protected]> wrote: > >> David Nalesnik wrote Saturday, November 01, 2014 10:53 PM >> >>>To work, \offset needs access to a default value--a number, >>> number-pair, or list of number-pairs--or a default procedure to calculate >>> these values with. If you don't find an entry in define-grobs.scm, it will >>> have nothing to work with. >>> >>> DynamicLineSpanner.padding works because it's set by default to 0.6. >> >> Hm. I wonder if it would go badly wrong if it simply assumed 0 in >> such cases? Or #'(0 . 0) - whatever it was expecting. You'd have to assume >>the form given in the passed offset value was correct, I suppose. In >> other words, work as if it were \override or \tweak. > > Wouldn't it just be duplicating the effect of an ordinary override of the > property?
Well, yes. But the point of \offset is that the user doesn't know and doesn't need to know what the default value is or whether it has a default value or not. He or she just wants to shift it a little from where it currently is. > Would this be a better behavior than what happens currently--maybe > give a warning "no default found, using 0.0" and at least do something nice? I don't think a warning would be necessary (assuming you find it works well). It would do exactly what the user was expecting. > Actually, it might not be hard to enhance \offset to deal with Script. > The defaults aren't stored in define-grobs, rather they're in script.scm. > I'll look into that. Great! I've just found two good examples serendipitously with layout queries from Noeck. So I'll work with them. Tomorrow. It's late. Trevor _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
