On 06/20/2015 09:43 AM, Ted Felix wrote: > I think I need a history lesson... > > I'm working on CompositionView::getFirstItemAt() and I've encountered > code related to dealing with segments appearing on top of each other on > the segment canvas. Specifically, CompositionModelImpl::getItemsAt() > can return multiple segments if there happen to be more than one at the > requested point. > > I can't find a way to test this. When I put two segments at the same > time on the same track, the track expands vertically ensuring that they > do not overlap. Was segment overlapping old behavior that was replaced > with the expanding track behavior that we have now? Is it safe to clean > up all the code related to overlapping segments? Or is there still some > feature/case (other than the SegmentMover tool) where segments might > overlap? > > Ted. > > ------------------------------------------------------------------------------ > _______________________________________________ > Rosegarden-devel mailing list > [email protected] - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-devel > Ted:
I think you can test this by doing an over-dub recording into a track (and position) already occupied by a segment. It creates a new segment below (or above) the existing one. You can merge the segments, but beware of pedal-down/pedal-up control messages. It can really mess up a track when you merge segments containing them. -- Sincerely, Aere ------------------------------------------------------------------------------ _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
