Chris Cannam wrote:
But however it works, it does actually work, right?
Yes, but it has pitfalls.
So what's the difference between that and the segment changing while it's
recording? How come, when the segment end marker time changes, we don't
automatically get a nice cheap repaint of just the segment's area without
having to do any more work at all? What's causing the entire buffer to be
redrawn in the first place?
Other update requests which are buffered along with the one for the
segment request, and are then processed altogether when the repaint
occurs. I've looked at *CompositionModelImpl::eventAdded() and
CompositionView::slotUpdate*(*const* QRect& rect), and both do what they
should, so it's definitely some other wider update request. It used to
be the one from setPointerPosition(), but you fixed that so I really
don't know.
-------------------------------------------------------
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
