Bug 496412 - Entering large numbers, unexpected behaviour
Summary: Entering large numbers, unexpected behaviour
Status: RESOLVED DUPLICATE of bug 495232
Alias: None
Product: kcalc
Classification: Applications
Component: general (other bugs)
Version First Reported In: 24.08.2
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Gabriel Barrantes
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-18 10:38 UTC by Juergen
Modified: 2024-11-18 15:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screenshot of the calculator (48.12 KB, image/png)
2024-11-18 10:38 UTC, Juergen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Juergen 2024-11-18 10:38:06 UTC
Created attachment 175907 [details]
screenshot of the calculator

SUMMARY

I expected the x*10^y button works like in other calculators the EXP Button to enter the exponent of a number like
2e6. Without am EXP button or an equvalent it is error prone to enter big or small numbers like 2e-7. 
Using the kcalc x*10^y button I get something like this 2*10^6, typically a calculator uses 2e6 which is (2*10^6). The display of the number in kcalc (see screenshot) suggests that it is an alternative to the 2e6 representation. If this number ends up in a divisor one gets a huge error. 
Kcalc uses anyhow this kind of number representation for its results.
  
In kcalc it works like this:
1/2 * 10^6 = 500000

I would like to have 
1/2e6 = 2e-7

STEPS TO REPRODUCE
1. Enter: 1
2. /
3. 2
4. Press the button: x*10^y
5. 6
6. =

OBSERVED RESULT
500000

EXPECTED RESULT
5e-7

SOFTWARE/OS VERSIONS
Linux 6.11.5-2-default (64-bit)
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Comment 1 Gabriel Barrantes 2024-11-18 15:53:20 UTC
Although this is not technically a bug,  I will see if something can be done as people seem to expect it to take priority, check the other bug report to see the full explanation.

*** This bug has been marked as a duplicate of bug 495232 ***