Scientific notation

Create issue
Issue #734 resolved
Former user created an issue

Typing 2e-1 returns 4,43656365691809047072. It treats "e" as the constant.

Typing 2e+1 returns 20.

So, when typing "e" the popup shows the constant unless it is followed by the plus sign which then becomes the scientific notation e.

SpeedCrunch master (Qt 5.8.0)

MacOS 10.12.5 (16F73)

Comments (23)

  1. Helder Correia repo owner

    Can't reproduce either. Maybe @sgaist on macOS? We need confirmation from OP about the app version though.

  2. Joris Lammers

    I run into the same issue. This is on OS X 10.12.5.


    See for example the last but one entry in the calculator: 3e-2 equals 6.15

  3. Joris Lammers

    Browsing through the code I figured out that the fix was not in the published OS X dmg for release 0.12. Built from source and now it works!

  4. Helder Correia repo owner

    Unfortunately, the only developer on the macOS side is @sgaist , let's wait for his comment.

  5. Samuel Gaist

    Sorry for the late reply, I lost the notification.

    One possibility would be to tag a 0.12.1 version with the current master and publish that one.

    Replacing the 0.12 with the current master would create a difference with the other platforms which is IMHO not be a good idea.

  6. Samuel Gaist

    @heldercorreia It's likely a parsing issue however I haven't had the time to dig deeper to see exactly which commit fixed it.

    Maybe commit e8ae9a3b47c57dfa7bf22efb9844192ac3e3a8bb

    We should review what has been added since the release-0.12.0 tag, it might be worth a 0.13 release rather than a 0.12.1.

  7. Tey'

    I believe this is related to issue #729 which was also posted by a MacOS user. Both issues should be merged I think.

    AFAIK, the MacOS release has been published after other releases (Win/Linux), but using the source code from the master branch, not from the branch-0.12 branch. That's why the MacOS release contain that bug while the other releases do not.

    We can either rebuild the MacOS 0.12 release using the appropriate branch (but users with current MacOS version will have trouble while updating because of Unicode operators in history file) or build a new MacOS release using current master source code (provided it is stable enough). In the latter case, we should tag it differently (as @sgaist suggested) and probably produce new releases for other platforms as well.

    Or we can just wait for 1.0 to be released, which is expected to happen soon-ish IIRC.

  8. Tey'

    @Timothy Thompkins The issue is fixed in source code, but you have to wait for a new release to be able to see the changes on macOS. We have official-ish development builds for Linux and Windows, but not for macOS. As for the next official release, it is unclear when it will be available (I do not really understand what are the blocking points TBH).

    @Gabriel G did build a release from a more recent version of source code than 0.12 here. It should contain the fix for this issue. Please note we have no control over this release and cannot validate it, so use at your own risk.

  9. Log in to comment