On Wednesday 09 December 2009, D. Michael McIntyre wrote: > Confirmed. segment->getKeyAtTime(insertionTime) is always returning the > first key I set at time 0. insertionTime looks sane and so on. > > Investigating. Good catch.
Hrm. insertionTime looks sane (ie. it's not always zero and the further I get from zero the bigger it gets) but Segment::getKeyAtTime() is always returning the key at time 0 in notation, but Segment::getKeyAtTime() returns something sensible from the matrix in every test I've made. Same code. Same segment. So with that knowledge I set up another test example with three key changes in a row, and this time it's passing Julie. WTF? Can you play around a little more and see if you can get it to work sometimes? Most of the time? This looks like something pretty subtle and evil, and if we can confirm it's "mostly working" I'd probably be prepared to gloss over it for now. If something is going wrong in base/ in ancient well-tested code, well, that ain't good. -- D. Michael McIntyre ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Rosegarden-devel mailing list [email protected] - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
