On Tuesday, December 20, 2011, [email protected] wrote: > Testing should include deleting tracks, undoing the addition of tracks, and > continued use of the software noting any problems.
I tried what I could to mimic problems we've seen before, including adding, deleting, moving, undoing, saving, reloading, and so on. Everything works fine in these tests, but until you add a complicated chain of random user actions in between A and B, you just don't really know how it's going to fare in the real world. It's promising anyway, and it might even turn out to be rock solid. > Feedback on this will help shape future changes. I am particularly > concerned about the notification responsibilities being shifted outside of > Composition. I think it's an ok move for a large system like rg. Others > might not. Dissenting opinions and discussion appreciated. The approach is a little odd, but I find myself nodding and thinking why not. It works. It probably works better, and it's certainly easy enough to follow. Looks like a job well done to me. -- D. Michael McIntyre ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
