On Monday 12 Dec 2005 17:18, Guillaume Laurent wrote: > I tried adding a > 'if (recording) segmentDrawBufferNeedsRefresh()' in > CompositionView::setPointer(), and that will put us back in CPU-hogging > mode just the same.
Point is, it shouldn't make any difference logically whether we're recording or not. Only one segment has changed -- in this case the recording segment's end marker time has changed (or whatever equivalent modification we may cook up) -- and so only that one segment needs to be refreshed. Why doesn't that work? > However, it seems pretty daft to me to update N segments with > essentially the same information, which will all trigger a screen > update, etc... Except that they should all trigger different screen updates, covering only their own areas, and so the net amount of work should be no more. Besides, surely we should optimise for the common case where only one segment is being recorded -- if recording more segments takes more CPU, that's forgivable. 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
