On Monday 12 Dec 2005 16:43, Chris Cannam wrote: > The thread actually _does_ throw away duplicate requests that have the same > notify callback (i.e. that originate from the same object) -- see > audiopreviewthread.cpp:156
Actually, I don't think it should even be doing that. It should be perfectly legitimate (from the point of view of the audio preview thread) for the same object to request more than one preview of the same segment at the same time (at different widths, say). More correct, structurally speaking, would be for the composition model always to use the same updater object for a given segment. Then AudioPreviewUpdater::update() could start by cancelling its previous preview request if its preview token was >= 0. Chris ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
