On Mon, 2005-09-26 at 19:27 +0100, Chris Cannam wrote: > * Single-click with fretboard tool on an existing fretboard opens > fretboard editor on that fretboard (just as you originally coded -- > sorry about that)
My code did not do this. I am more for a double-click doing the editing > * Single-click with fretboard tool in empty space opens fretboard > editor for a new fretboard (also just as you originally coded) I can change that back. > * Fretboard tool needs to change the mouse cursor (to what, I wonder?) > just as the text tool and others do > * Double-click with selection tool on an existing fretboard does > likewise (does this work for text? I can't remember. It should) My intent is to edit an existing fretboard by opening the editor via a double-click. > * Single-click with selection tool on an existing fretboard selects > that fretboard (I would expect this to work by default). Ok. > > b) Provide ability to drag fretboard from one location to another > > This may not be necessary -- the existing micro-positioning > (shift-click-drag) might already work. I haven't had a moment to try > it. I will have to try the shift-click-drag and see how it goes myself. > By the way, I have a point of conceptual confusion about the fretboard > editor. Let's say you open it and select a known chord through the > selection boxes at the top. Then you edit the chord on the fretboard, > so as to end up with something totally different. But the name of the > chord you started from is still shown above, even though it's now > completely different. So what is actually stored in the composition > when you apply the dialog? At that event position the chord you modified would be stored. > Does it record the formal name of the known chord you started from, or just > the modified fingering? It records the modified fingering. The naming is used to help you select the original chord in the first place. > Is there any way in the GUI to assign a new name to a modified fingering? (I > guess > that has to be part of the plan, along with saving them out to file.) For now I have all new chords being added via the xml files. I had not gotten that far to consider how I can allow users to add new ones. My original thought was that rosegarden would provide all the original XML files. When the user used the guitar tab editor for the first time it would read the original XML files to populate a single user XML file (e.g. rosegarden_chords.xml). If a user adds a new chord we could simply rewrite the file. if rosegarden_chords.xml is not found - read original xml files - write user rosegarden_chords.xml else - read user rosegarden_chords.xml If new chord added - write user rosegarden_chords.xml > I'm just vaguely wondering whether somewhere, deep down in the .rg > file, there's always going to be something faintly identifying your > completely spurious chord with the nice plain C major you started with > when creating it. I hope you see that the name is not recorded only the fingering is in the .rg file. Stephen
signature.asc
Description: This is a digitally signed message part
