Menu
▾
▴
[Scstudio-devel] [ scstudio-Bugs-3067517 ] Large numbers in time constraints - visio deformation
|
From: SourceForge.net <no...@so...> - 2011-11-28 00:29:16
|
Bugs item #3067517, was opened at 2010-09-16 04:26 Message generated for change (Settings changed) made by obouda You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3067517&group_id=219467 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Visio Interface Group: None Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: Vojtech Rehak (xrehak) Assigned to: Martin Vodila (martinnrt) Summary: Large numbers in time constraints - visio deformation Initial Comment: When a visio drawing is redrawn from internal structure (repaint, result presentation), large numbers are deformed into exponential form, i.e. 1.23453e+12. ---------------------------------------------------------------------- Comment By: Ondřej Bouda (obouda) Date: 2011-11-27 16:28 Message: The type numbers are converted to is double, Which means that numbers like 12345789012 should not be parsed without loss of precision. Which means such a number is still stored exactly as specified, but only presented with precision loss. Which means this is rather an annoyance in the frontend. ---------------------------------------------------------------------- Comment By: Vojtech Rehak (xrehak) Date: 2010-11-01 07:36 Message: It is OK for now. For the future, we need to note somewhere what is the exact precision we are working with. The problem is that Martin Vodila is currently working on extraction of bMSC from test logs and he decided to use unix time in milliseconds which I guess is out of our current precision. ---------------------------------------------------------------------- Comment By: Petr Gotthard (gotthardp) Date: 2010-09-21 00:52 Message: This is not a bug. This is a feature. Exponential form is (now) correctly handled by parser. Is there anything that we should fix here? What is the desired behaviour? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=1046486&aid=3067517&group_id=219467 |
