On Fri, Jan 2, 2009 at 1:56 AM, Julie S <[email protected]> wrote: > In trying to reduce some errors in the port, I started converting some of the > code to the leaveActionState() and enterActionState(). In RosegardenGUIApp > these are stubbed out. This is also the case in EditViewBase.
Oh, cool. > Could you shed a little insight as to how this is going to unfold? Well, the idea is just that any class which may wish to call these functions will have them available in its own scope by some means or other. In some cases that means it will be a subclass of something like EditViewBase; other classes may have some other base class in which we can put these functions. In each case the functions themselves will probably be one-liner calls off to an action management object (which is where my ActionFileParser class will come in). It's always going to be possible to make a literal enterActionState() call work somehow! In other words, the direction you've taken is the same as the one I was hoping to go. So it's all good. Thanks. Chris ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
