Bug 498190 - Scientific calculator history display format is garbled
Summary: Scientific calculator history display format is garbled
Status: RESOLVED DUPLICATE of bug 489191
Alias: None
Product: kcalc
Classification: Applications
Component: general (other bugs)
Version First Reported In: 23.08.5
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Evan Teran
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-03 01:18 UTC by deusexaethera@gmail.com
Modified: 2025-01-10 07:33 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description deusexaethera@gmail.com 2025-01-03 01:18:14 UTC
SUMMARY
The calculation history display format for the scientific calculator mode displays the entered values and operations out-of-order, making it very difficult to double-check what I've entered.

STEPS TO REPRODUCE
1. Enter any sufficiently long sequence of values and operations. See "EXPECTED RESULT" for an example.

OBSERVED RESULT
7664.9 - 2098.37 - 90.8 - 49.99 - -903.53 = 1934.86  -41.66  -750  -300  -300  -70.26  -123.45  -426.94  -363  -61  -74.35  76.69

EXPECTED RESULT
7664.9 - 2098.37 - 90.8 - 49.99 - 76.69 - 74.35 - 61 - 363 - 426.94 - 123.45 - 70.26 - 300 - 300 - 750 - 41.66 - 903.53 = 1934.86

SOFTWARE/OS VERSIONS
kinfo output:
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-51-generic (64-bit)
Graphics Platform: offscreen
Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz
Memory: 23.4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530

ADDITIONAL INFORMATION
The result is correct; only the calculation history is out of order.
Comment 1 John Kizer 2025-01-10 07:33:42 UTC
Hi - I cannot reproduce this issue on the current version, and this appears to be an issue that was fixed a couple of versions ago - merging in with the bug where this was reported and confirmed fixed by the developers, thanks!

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