On a similar note to the previous bit of optimisation: is it worth spending a bit more time making sure there isn't just something in the view destroy/create cycle that's taking far more time than it should?
Does it do much work between the destroy and create? I'm seeing this interesting buglet at the moment that I hadn't got around to reporting: I run RG with --nosequencer, but it still pops up an occasional dialog saying "Failed to contact Rosegarden sequencer". That's not a big problem, but what is interesting is that one of these always pops up between the view destroy and create when loading a new document, suggesting there is rather more work going on there than is really desirable. (Another identical dialog pops up as soon as the new view has been created.) 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
