On Tuesday 30 September 2003 21:10, Chris Cannam wrote: > > It's now used in exactly one place: Segment::setTrack. But isn't that > actually a place where we _do_ want to update the refresh statuses?
Yes, but Composition::detachSegment() also calls notifySegmentRemoved() (and addSegment() calls notifySegmentAdded()), which will cause the segment's mmapped file to be needlessly removed and recreated. So you're right, we do need to update the refresh statuses, but the notifications should not be triggered. > That looks like the cause of this bug: > > https://sourceforge.net/tracker/?func=detail&aid=778332&group_id=4932&atid= >104932 I've added a call to Composition::updateRefreshStatuses() and I can't reproduce it anymore. -- Guillaume. http://www.telegraph-road.org ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Rosegarden-devel mailing list [EMAIL PROTECTED] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
