Re: Manipulating instrument names and staff group names, Thomas Morley, 1.Re: Manipulating instrument names and staff group names, Valentin Petzel, 1.Re: Manipulating instrument names and staff group names, Kieren MacMillan, 1.I'd be happy to try my hands on this a bit. The first option wished for by Adam (horizontal alignment of all theīrackets) is very easy to implement this is just a matter of fixedĪs Harm already stated that he won't have time to work on this for now, This requires a separate implementation of the two options. Increase the padding for the single staff names. For the second option, the GroupName machinery has to ![]() GroupName has to know the extents of all the single-staff Layout problems: For the first option, the machinery creating the Single staff names on the outside ("on the left"). Vice versa: group name with bracket on the inside ("on the right"), and The right"), group name with bracket on the outside ("on the left") and To mind which should both be supported: Staff names on the inside ("on The hard part seems to be horizontal spacing. Vertical ("rotated") printing of the Group Name should be available asĪ boolean option, not depend on manual markup rotation. Maybe StaffCollection would be a suitable name? SystemStartBracket etc.), and from which StaffGroup and all the otherĬontexts should be derived. Logical grouping and has no hardwired visual grouping elements (SpanBar, I think this is a good opportunity to add something I've wantedįor a long time, namely a staff grouping context that provides _only_ Might be reasonable not to have SystemStartBracket's etc. Grouping staves visually by a bracketed instrument name means that it \consist the standard Instrument_name_engraver, whereas the groupingĬontexts should have the Group_name_engraver. Then could be changed such that only Staff (and TabStaff etc.) contexts The context definitions of StaffGroups etc. (Group_name_engraver?) that mimicks and extends the Might make it reasonable to create a dedicated engraver The ability to deal with the needs of multi-staff groups specifically Reasons of backwards compatibility, it should probably stay that way. New Layout object / by a new engraver, or if this should be added to theįunctionality of InstrumentName and the Instrument_name_engraver.Ĭonceptually, I was never really happy with the staff group names beingĬalled InstrumentName's, but I have to admit it's convenient, and for I'm not sure if "staff-group names with brackets" should be done as a We also both did not bother try to do the horizontal alignment the right ![]() In system-start-text::calc-y-offset, the standard callback for Necessary computations of the StaffGroup's total Y extent are contained (Probably we were both inspired by the fact that the ![]() Y-offset calculation using a procedure that changes the stencil as a What Harm provided: We both had the same cruel idea of hijacking the Well, the code I sent Kieren off-list was more-or-less equivalent to The good old methods: define two new grobs and an For a new featureĪdded to LilyPond proper, I don't see a way around Others, if they’re offered - with an eye to eventually submitting a Maybe we can/should discuss the pros and cons of each approach - and Lukas sent me a totally different solution that was also Nice! This definitely solves the basic problem nicely. Re: Manipulating instrument names and staff group names
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |