On Sunday 20 September 2009, Chris Cannam wrote: > i is a Composition::iterator, so *i is a Segment pointer.
> Segment::getTrack() returns a TrackId, unsigned, and should never > return an invalid value. Right, right, the other one is a red herring, the easiest thing to find with a search. Now that you remind me, this all feels like familiar ground. Segment.h has this implemented inline, which is why it's trickier to find. Try "getTrack" and you get a million returns for getTrackById and getTracks and so on, so you try to focus the search by looking for where it's implemented, and find the CompositionTimeSliceAdapater and if you're not paying careful attention... Anyway, I agree that it would be strange if removing the >= 0 test changed anything. I went through this myself quite some time ago, and I don't remember what I thought I experienced at the time, but I can't find any problem with doing that now. -- D. Michael McIntyre ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
