On Mon, Jan 07, 2013 at 02:26:39PM -0500, D. Michael McIntyre wrote: > On 01/07/2013 11:56 AM, H. S. Teoh wrote: > > > I know I can edit the lilypond output by hand, but it'd be nice to > > not have to manually do this every time I export from rosegarden. > > If you would, grab and build a copy of the development source, and > test this out.
Thanks for your prompt response! Sorry for taking so long to reply; I just got home and am trying to figure out how to build Rosegarden from source. Just managed to coax it to find the Qt libraries on my multi-arch Debian system (which causes a lot of build scripts to fail due to unexpected locations of libraries -- most notably, it causes hours of hair-tearing grief with gcc's build system). Anyway, rosegarden is building now, and with any luck, I should be able to test it tomorrow and get back to you about how things went. :) > I knocked together a new option and set it up so inserting this > snippet in the layout block is the new default behavior. You don't > have to do anything to turn it on, but if you really want to print all > the empty staves, you can suppress the new behavior by turning a > checkbox on. > > I banged this out in a hurry and did only extremely minimal testing. > There could be lots of problems, and it would be extremely helpful if > you could put it through its paces and reassure me that it's > reasonably robust and predictable. I'll get back to you once I try it out. Thanks! > Thanks for requesting something that was clearly reasonable and only > took 30 minutes to bash together. It would have only taken 15 minutes > if I had read your original message more clearly the first time. I > wasted time putting the new code snippet in all the wrong places at > first. Oh well. [...] Speaking of which, what's the usual way of debugging crash problems with rosegarden? I date back from the X11 rosegarden days, where misaligned notes can cause segfaults, and I have to say rosegarden has come a looong way. :) But yesterday, I got a segfault while trying to fiddle with moving segments around tracks -- y'know, grappling with notation problems as usual -- it doesn't happen now, but I thought it'd be nice if I know what to do if I figure out how to reproduce the crash and how to hunt down the problem, so that it can be fixed for future users. T -- To provoke is to call someone stupid; to argue is to call each other stupid. ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of 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_122512 _______________________________________________ Rosegarden-user mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-user
