On 05/04/2014 01:40 PM, Tom Breton (Tehom) wrote: > I like Aere's and Michael's idea of just balking and maybe popping up a > warning, but it's hard to detect that situation before the command has > run.
If it's hard to figure out ahead of time if what the user said to do will come out badly, I'm totally in favor of just letting them figure it out on their own. That's what undo is for. The only drawback is that it's quite easy to lose things from selections or lose entire selections when you go through this process of trying different commands and hitting undo. It sucks when you have a very tricky selection you spent half an hour making, and you ended up with no selection, and have to make it all over again. I can't remember if we ever did anything in that general area or not. Anyway, working on anything related to that kind of arcane memory allocation pointer stuff is a job best left to anybody but me. > So I'm leaning towards Michael's other suggestion: Build the hideous > series the user asked for and let him undo it. You can never go wrong that way. This is Rosegarden, not a tire shop. If the user wants to put 24" rims on his 1983 Honda Civic and wrecks as a result, we get to laugh at him, because we're volunteers. Sucks to be you, dumbass. -- D. Michael McIntyre ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
