More info, this algorithm is actually wrong altogether. With my recent commit, the final position will be correctly returned as 1.0, but frames just prior to it will be greater than 1.0, which is clearly wrong.
On Sun, May 6, 2012 at 12:44 PM, Michael Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > I noticed today that this function is broken at 1.0 (final frame) using > ECORE_POS_MAP_ACCELERATE; it doesn't return 1.0 as it should, and thus the > final frame is never reached. I've committed an amazingly hackish fix, but > feel free to modify it if there's a slower, more mathematically correct > solution. > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
