Richard Bown wrote: > Well the extra processEvents() doesn't seem to make any difference here
Interesting. It makes a huge difference here, especially with MIDI file loading where we really were/are doing a significant amount of work (notation quantization) after the view was created but before any events had had a chance to percolate. I guess there are two different effects at work -- the grey-screen effect (big pause between one view disappearing and the next appearing) and the flicker caused by the fact that the view is being replaced at all. It's presumably true that we can't avoid the latter without avoiding destroying the view, but we should certainly be able to do quite a bit about the former. You haven't made clear which of these is particularly bothering you -- I happen to have little problem with the flicker myself, though obviously it'd be nicer without. > There is something inherently wrong though with throwing away > all that good stuff just because we've got a new document As I said, I can't escape the suspicion that we may eventually want the view to stick around to correspond with a document that's sticking around too. But maybe it's just a question of which way you slice your document-view interface. Chris ------------------------------------------------------- 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
