On Thursday 10 July 2003 09:41, Richard Bown wrote:
> 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.
Actually what we had before the current "dumb and simple" mechanism was a
clever one where every view would dynamic_cast<> commands from the undo stack
'til they were blue in the face trying to figure out if they should update or
not.
This was replaced by the current mechanism which is simply "hey, update
yourself 'cause something has changed". The only clever bit we have are the
refresh statuses which the edit view use to know what time span they should
update.
So I'm not sure what you would like to have. IMHO the current mechanism is
fine for edit views, but I agree we could think of something a tad more
elaborate for dialogs. For instance, some sort 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.
--
Guillaume
http://www.telegraph-road.org
-------------------------------------------------------
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
