Bug 488037

Summary: [Feature] Allow/Add group separator in input display.
Product: [Applications] kcalc Reporter: Marian <marian811>
Component: generalAssignee: Gabriel Barrantes <gabriel.barrantes.dev>
Status: CONFIRMED ---    
Severity: normal CC: axel.braun, bugsie, enricobe, gabriel.barrantes.dev, jgqehj55, kdebugzilla
Priority: NOR    
Version First Reported In: 24.05.0   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=488167
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Marian 2024-06-04 20:13:44 UTC
SUMMARY

In 24.05.0 it's no longer possible for me to use a large pasted number with a delimiter (a dot that seperates group of thousands) and use it for a calculation. It produces an "input error". In previous versions KCalc was able to use these numbers.

It doesn't even matter if the delimiter is a dot or a comma.

STEPS TO REPRODUCE
1.  Copy a large number that has dots in it that seperate group of thousands, like "2.560.275.623"
2.  Paste it into KCalc
3.  Divide by 1024

OBSERVED RESULT
KCalc says "input error"

EXPECTED RESULT
It should be able to calculate "2560275623 / 1024" and give "2500269,16309" as a result, just like older versions of KCalc.

SOFTWARE/OS VERSIONS
Manjaro
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION
It used to work in older versions just fine!
Comment 1 Gabriel Barrantes 2024-06-26 02:28:52 UTC
*** Bug 488167 has been marked as a duplicate of this bug. ***
Comment 2 Gabriel Barrantes 2024-08-16 03:00:50 UTC
*** Bug 491645 has been marked as a duplicate of this bug. ***
Comment 3 Gabriel Barrantes 2024-09-01 03:09:23 UTC
*** Bug 467984 has been marked as a duplicate of this bug. ***
Comment 4 Gabriel Barrantes 2025-07-01 15:29:19 UTC
*** Bug 506424 has been marked as a duplicate of this bug. ***
Comment 5 Enrico 2025-09-01 14:15:33 UTC
Hello, the missing "thousands separator" gives to Kcalc a very poor user experience IMHO. I see that all the other bug reports are marked as duplicate of this bug. I hope someone can work on this fix. Thanks a lot!