On 10/12/2013 07:54 AM, Niek van den Berg wrote: > As a woodwind player (clarinet Bb/A and altsax Eb) I know the concept of > transposing instruments :-) One of the reason I liked to see transposable > chords.
Very good. I'll shut up about what you already know. > I noticed this too and have a closer look at it. I'm using currentKey in > NotationStaff::renderSingleElement but for some reason it is sometimes > "undefined" instead of the current key. I bet that's the heart of it. You're displaying correctly when you have the proper key. I have no special insight into why it is undefined sometimes. > Exporting this chord to LilyPond and MusicXML is what I'm current working on. You probably know just what I mean, but I want to make sure you understand how the lead sheet chord names feature works. I imagine users would love having an easier way to do that, although I haven't used that myself. > I had already something similar on my wishlist, but I didn't think of a filter > during file load. This might make things even better. A filter during file load seems like an ideal solution to me. If we preserve the information from the old legacy file, we can drop support for the legacy LilyPond export option, and have one less piece of clutter, and one less situation where there are multiple ways of doing exactly the same thing. -- D. Michael McIntyre ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
