On 01/12/2013 12:12 PM, H. S. Teoh wrote: > Much much better!! The very first page looks a bit odd with so much > space, but I'm not too worried about that (better too much space than > truncated text, that's for sure).
Agreed. The truncated text was always severely annoying. > Hmm. I'm surprised Lilypond doesn't have a way to automatically allocate > space based on how long the text is. You're more than welcome to go trolling the LilyPond docs for yourself, but I couldn't find any such thing. > I think in this case, manual controls are an inferior solution. I agree in spirit... > They didn't?! I'm surprised. ...but we've always just thrown the staff name up there in the most obvious and simple way, and left LilyPond to do the layout magic. It has always done a wretched job with long staff names. It obviously doesn't even try, and just leaves it to the user to RTFM and figure out how to override the spacing, and diddle it to taste. I agree completely that an automagic solution is best, but LilyPond is what has access to all the details about how long a given string in a given font at a given size is going to be, and it seems kind of futile for Rosegarden to try to make educated guesses one layer removed from all the raw data. It's tempting to try anyway, but I don't think I will, because it just seems so unlikely to work out well. If at any time it errs the wrong way on spacing, we're back to needing a manual control. > Anyway, yet another related question: how do I make very long staff > labels wrap to multiple lines? Is this even remotely possible? That's an interesting possibility. It IS possible in LilyPond... > Also, I'd like to use a flat symbol (like "Trumpet in B♭" as opposed to ...and so is that. Both would require some thought and doctoring. The latter is especially interesting. We already have all this staffNameWithTranspose stuff that adds the "\smaller \flat" to the strings, but it doesn't seem to do anything. If it did work, it would need to be made smart enough to get itself out of the way if the user writes the "in Bb" part manually. No time to look into that just now, but I'll try to remember. As to the multi-line thing, I'm thinking about that. One possibility is to add a third field. track name [ ] note [ ] short name [ ] That sure is a huge PITA, but I just made the map to follow. Another possibility is to allow the user to just enter \n in the string and interpret. Trumpet\nin Bb That would git'r done, but it would look like crap. Hrm. I'll mull that over. I gotta go earn some money now, unfortunately. -- D. Michael McIntyre ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 _______________________________________________ Rosegarden-user mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
