On Thursday 10 July 2003 3:08 pm, Guillaume Laurent wrote: > some sore of "central signaling class", which would broadcast changes on > data structs other that the composition (studio stuff), and to which > dialogs would connect their slots.
Ok that's fine but I'm more worried about how to update the main segment view and rulers elegantly than updating the dialog themselves - at the moment we just force the rulers etc. to repaint. What would be nice is we had a nice common gui mechanism (or mix-in) that we could derive them from too - so all gui components that are interested in a certain type of data update on request. This at least is a simple enough solution - create a new class for GUI updates, perhaps subclass it per data type (Controllers, Markers, Tempo changes etc) and make all those classes that need a prod derive from it. Alternatively we could have a central update class aware of the various types of data and a map from GUI component to type. Not quite as simple as passing around signals and connecting slots directly but perhaps a little more obvious? It's certainly not obvious at the moment and although the Event/Segment stuff works there (as I think you're both saying) is a need for a new way of distributing these requests reasonably elegantly. 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
