{"action":"closed","issue":{"url":"https://api.github.com/repos/openfl/actuate/issues/38","labels_url":"https://api.github.com/repos/openfl/actuate/issues/38/labels{/name}","comments_url":"https://api.github.com/repos/openfl/actuate/issues/38/comments","events_url":"https://api.github.com/repos/openfl/actuate/issues/38/events","html_url":"https://github.com/openfl/actuate/issues/38","id":38102948,"number":38,"title":"margin of error?","user":{"login":"SavedByZero","id":3465578,"avatar_url":"https://avatars.githubusercontent.com/u/3465578?v=3","gravatar_id":"","url":"https://api.github.com/users/SavedByZero","html_url":"https://github.com/SavedByZero","followers_url":"https://api.github.com/users/SavedByZero/followers","following_url":"https://api.github.com/users/SavedByZero/following{/other_user}","gists_url":"https://api.github.com/users/SavedByZero/gists{/gist_id}","starred_url":"https://api.github.com/users/SavedByZero/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SavedByZero/subscriptions","organizations_url":"https://api.github.com/users/SavedByZero/orgs","repos_url":"https://api.github.com/users/SavedByZero/repos","events_url":"https://api.github.com/users/SavedByZero/events{/privacy}","received_events_url":"https://api.github.com/users/SavedByZero/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2014-07-17T16:50:47Z","updated_at":"2015-01-01T21:40:08Z","closed_at":"2015-01-01T21:40:08Z","body":"I'm working on a project that depends on timing down to the millisecond (or pretty close), and I noticed that Actuate.tween isn't completely precise.  On the XCode simulator and my iPhone itself, if I tell it to tween for 600 milliseconds (0.6 seconds), it'll be anywhere from 632 milliseconds to (rarely) 700 milliseconds.   Is this normal behavior?  Is there a more precise way to tween?"}}