Re: Big integers exported in scientific notation in XML
site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Yes. We know about that one. -eryk (from my iPhone) On Sep 2, 2009, at 17:29, Bruce Sharpe <bruce.sharpe@gmail.com> wrote: Example: Expected value: <duration>1234567</duration> Exported value: <duration>1.23457e+06</duration> Is this a known bug? Bruce _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/evershen%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... I have just discovered that if a project contains a clip that has more than a million frames (4.6 hours at 60 fps would do it), then numbers like duration, in, out, etc. will be exported in the XML in scientific notation. Aside from the fact that it messes up everyone who is expecting an integer there is a loss of precision. The difference between 1234567 and 1234570 frames could be important in some contexts. This email sent to evershen@apple.com This email sent to site_archiver@lists.apple.com
participants (1)
-
Eryk Vershen