Darkempire78 / OpenCalc

A simple and beautiful calculator for Android
GNU General Public License v3.0
740 stars 83 forks source link

Decimals cause value errors #114

Closed is-code-afish closed 1 year ago

is-code-afish commented 1 year ago

In latest version, adding a decimal to a number will add an unexpected and incorrect "0" to every value left of the decimal.

Darkempire78 commented 1 year ago

Try using the v2.0.0-beta3 it must be fixed

is-code-afish commented 1 year ago

I can re check, but I believe I'm on the latest version on f-droid, or what it claims as such. Edit: I am on V2.0.0-beta2, issue is still present.

Darkempire78 commented 1 year ago

The issue is fixed for me, are you sure ?

is-code-afish commented 1 year ago

Screenshot_20221201-114922_Calculator Screenshot_20221201-114925_Calculator Screenshot_20221201-114948_Calculator Screenshot_20221201-114955_Calculator Issue still persists. When adding a decimal, or changing the digit following the decimal, it adds an unexpected 0 to the left of the decimal. This is likely a bug involve a QOL feature that adds a 0 when adding a lone decimal, but it isn't disabling the feature when there's already digits present.

is-code-afish commented 1 year ago

Screenshot_20221201-115438_Calculator this qol feature. Screenshot_20221201-115458_Calculator It works properly when there is only 1 previous digit Screenshot_20221201-115500_Calculator

Darkempire78 commented 1 year ago

I'm not able to reproduce it ( I tried in French and English)

eXense-auth commented 1 year ago

try russian please

Stalthdan commented 1 year ago

I've encountered this issue too, I'm on version 2.0.0-beta2.

Try entering 4004.25 It'll show up as 40,040.25 Then when erasing up to the decimal, is changes to 400,400

My system language is English (United Kingdom), running Android 9.

Darkempire78 commented 1 year ago

@eXense-auth @Stalthdan This version should be fixed in the v2.0.0-beta3, can you confirm me taht it was fixed ? I'm not able to reproduce it since the beta3

Stalthdan commented 1 year ago

@Darkempire78 Yes, it seems to have been fixed in v2.0.0-beta3.