MiHeGo wrote:Logged off before I could submit my completely typed reply !
andrew wrote:When are these coordinate changes happening?
andrew wrote:...I can imagine that the inaccuracy was already present in the QCAD 2 file
andrew wrote:- Small errors introduced when scaling entities up and down or rotating them...
andrew wrote:- Computers cannot represent all values (not even finite decimals) internally due to the way how they store numbers
MiHeGo wrote:andrew wrote:...I can imagine that the inaccuracy was already present in the QCAD 2 file
Actually, most of my values were typed as integer, some times at most with 2 decimals. If I change in Q3 a value like "281,999967" into a "281" and save the file, close Q3 and reopen the file, the integer value is there as "281" and not some "281,000000" and not scaled or adjusted to some internal number. What Q3 can do when processing its values, why is it impossible when opening a Q2 file ?
MiHeGo wrote:andrew wrote:- Computers cannot represent all values (not even finite decimals) internally due to the way how they store numbers
Sorry, this time, I have to completely disagree with that position. As a professsional programmer for 40 years (and more to come), I had never a problem storing and retrieving integer values or fixed decimals ones. Merely a matter of selecting the right data type.
For instance an Ariane missile was lost because some internal routines were using 64-bits arithmetic and values where others were using 128-bits precision.
Simply, would you accept to receive a payement of an amount of 23,99 swiss Francs (QCAD 3 update) instead of 24,00 SWF ? Or a salary of approximately 4.999,98 € instead of 5.000,00 € ?
Users browsing this forum: Google [Bot] and 1 guest