At the moment there's lots of updating of dialogs/views going on by unfair means (raises hand feebly) i.e. not using any clever mechanism to update the relevent views or rulers but just forcing a repaint after the event. Of course this makes things ugly, non-Command driven and a bit messy. If we could change the Commands and Views in question (AudioFileManager, BankEditor and now ControlEditor, MarkerEditor) to use a proper update mechanism for the GUI things would be neater.
My question is how? I've been looking at the Observer stuff and it seems straightforward enough (at least attachment wise) but I'm at a loss as to how this works when it gets into the GUI. Does everything currently have to be a RosegardenCanvasView to benefit from Observers? In the case of (say) the top BarButtons when I want to force an update after I've dropped a Marker (new functionality) how should I implement an Observer in the BarButtons? R ------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
