From: D. M. M. <ros...@gm...> - 2013-09-03 15:29:27
|
Random thoughts from Captain Insomnia... I like the idea of detaching this new stuff from the legacy text chord mark entirely. Retain the old functionality, unaltered, change the name to "User Chord" or something. Invent something new. Maybe the new thing still uses text internally, because it's easy, but users don't edit the text manually. LilyPondDirective is an example of such. LilyPond directives were a cheap hack; I wanted to do something nicer, but I was lazy and even incompetent. They're horrible, but they work. Sort of. If you hold your mouth right. The new thing could combine LilyPond lead sheet chord dooflatchies with normal human chords, be one or the other or both separately. I don't know yet. Finally, I haven't checked what happens when a chord text mark is attached to an event, and you simply move the event somewhere else and change its pitch. What happens when the event is part of a chord? Say you have a C an E and a G and the C has a chord "C" over it, and you move the E to an Eb by selecting that note and hitting the down arrow to lower it one semitone? OK, so first of all, it's not a text mark, it's a text event. Shows how long it's been since I worked on this. Second of all, nothing happened here. Now I have a C over top of a C minor chord. I guess chord recognition is a whole entirely different kettle of fish. Doing nothing is much better than doing something stupid, so this works. I find myself having thoughts about all kinds of ways to automate what, but then I find myself realizing that sometimes it's better to make work for the user than to make everything immensely complicated trying to solve everybody's problems. The problem with users is there are 50,001 different ways to use Rosegarden, and pleasing everybody is a huge pain in the ass. Pleasing nobody is always the cheapest option. -- D. Michael McIntyre |