https://bugs.documentfoundation.org/show_bug.cgi?id=145499
--- Comment #8 from Colin <[email protected]> --- (In reply to Heiko Tietze from comment #7) > Don't see what UX input can add here. Taking the result of a floating number > calculation into the auto filter (or any other calculation) requires to > consider precision. It would be a user mistake to assume a certain number of > decimals. If GSheet (or other) does round it will (silently) fail in those > scenarios where the difference is crucial. This user utilised the LO Round() function on each and every preceding value, two of which are simply summed for the third value which appears in the Autofilter. The ERRONEOUS value was examined right out to the user available 15 digits and still didn't demonstrate the long decimal BUG. It would surprise me if NASA are utilising LOCalc for their trajectories to Mars so, making it fit for the normal user's purpose might be considered the objective . Also, it would surprise me if any user would be indexing 1234567890.012345678912345 And 1234567890.012345678912346 I don't really think it's fair to implicate the User. Would you disagree? -- You are receiving this mail because: You are the assignee for the bug.
