On Tuesday 03 June 2003 11:39, Richard Bown wrote:
>
> I notice there's also a note in App::setDocument when deleting the
> AudioManagerDialog saying:
>
> // TODO : replace this with a connection to documentAboutToChange()
> sig.
>
> Obviously someone's
Me. It's true the audio dialog is somewhat expensive to recreate, but simple
enough that it could conceivably just re-read the relevant info from a
changed document.
> thought about this before then. So any recommendations
> while I'm having a look?
To sum up, now this is over and done : what you were about to do (reusing the
widgets for each document) can be done but has way too many implications for
us to work on at this point. Even in the long term, while it could make sense
for things like the AudioDialog, I don't believe it does as a general scheme
because it's too complicated. We used to do "document->setComposition()" and
found that to be a pain in the ass. There's no reason to think that
"widget->setDocument()" won't be either.
What you ended up doing (building the new view "in the background" and then
switching them) was exactly what I was thinking of as a solution to this
problem (believe it or not :-) and works very well.
--
Guillaume.
http://www.telegraph-road.org
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Rosegarden-devel mailing list
[EMAIL PROTECTED] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
