Closed patrickhlauke closed 9 months ago
unrelated, but when running this locally, it kept showing me an error when trying to open the preferences
To get it to run locally, I had to uncomment lines 26 to 29 https://github.com/ThePacielloGroup/CCAe/blob/main/src/menu.js#L26 ... is this intentional somehow?
unrelated, but when running this locally, it kept showing me an error when trying to open the preferences
To get it to run locally, I had to uncomment lines 26 to 29 https://github.com/ThePacielloGroup/CCAe/blob/main/src/menu.js#L26 ... is this intentional somehow?
The commented code is intentional, but the error is not :)
(not sure why it decided that 2.952 actually rounds to 2.96 in this case...but nothing that I touched should have influenced that. EDIT: ah, it's likely this which accounts for the difference in rounding between the last release - first screenshot here - and the latest main branch - second screenshot, with my PR applied - 0cee4cc)
Might be related to my recent modification: https://github.com/ThePacielloGroup/CCAe/commit/0cee4cc5d00ef114963e0cc716cc28417d4c546d
I'll merge and to do some proper testing later, to see what I'm missing.
Currently, the "just below" text is displayed at inappropriate points when "decimals" is set to 2 (both in unnecessary cases, and - as seen in the screenshot below - just completely wrong cases, as 2.952 is not below 2.95)
It should only show if there's a rounding happening one decimal point below the currently set decimal display, and only if it's just below 3, 4.5, or 7.
This PR adds more nuance to the big
if
used to decide when to show the "just below" bit.(not sure why it decided that 2.952 actually rounds to 2.96 in this case...but nothing that I touched should have influenced that. EDIT: ah, it's likely this which accounts for the difference in rounding between the last release - first screenshot here - and the latest main branch - second screenshot, with my PR applied - https://github.com/ThePacielloGroup/CCAe/commit/0cee4cc5d00ef114963e0cc716cc28417d4c546d)