> It would take some thinking to work out a way to use the information for > this new purpose. The code does a really clean and efficient job of doing > what it was originally conceived to do, but it seems a bit awkward to adapt > it to this new purpose.
I was thinking about this at work today. I think this dialog is probably modular/reusable enough that the new code could just create an instance of it from wherever it is, and then query its widgets afterwards to obtain the necessary data. It might be a drop-in already, or might require just a little tweaking to make it so, but I don't think it will be as complex as I thought yesterday. I'm thinking of some kind of interface paradigm with a "Convert Part from Instrument X to Instrument Y" (except worded differently, surely) option somewhere. Basically you somehow dial up what the segment is now, and where you want it to go, by name. It would need to be clever about figuring out what kind of segment it already was, or what kind of segment it was trying to become. I'm not quite sure on that. Needs thought. -- D. Michael McIntyre ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
