Convert scientific notation to standard calculator how to#
Convert scientific notation to standard calculator code#
Convert scientific notation to standard calculator plus#

Convert scientific notation to standard calculator code#

To Microsoft: If you need some help, just send me your code and I will fix it for you, pro-bono. They would much rather you just suck it up like a good little user and let them fix it when and if they get around to it).

Convert scientific notation to standard calculator how to#

(They don't like it when other people point out how to fix (or side-step) their failures. But I don't dare point you at another calculator program that works correctly, because it might upset someone at MS. But like I've said in previous posts (that mysteriously get 'hidden' as 'off topic'), If you are waiting for MS to fix this, you are in for a very long wait. I think the original point of this thread was that SN is not suited to all circumstances or use-cases, and it would be nice if it was not forced upon us, especially when there is NO GOOD REASON for it. Try toggling the F-E button on the value for Pi to see what I mean.

Convert scientific notation to standard calculator plus#

Using it on a value with Integer digits (or not) plus lots of decimals (with or without zeros to the right) is an exercise in stupidity because the SN version is actually longer, and if anything is harder to read, not easier ('How many places do I need to shift that decimal to get my real value?'). As far as I understand it, SN syntax generally only has a few decimal places included, and is best used to represent values with Zeros to the right OR many digits to the left of the decimal, like 0.000125 (1.25E+4) or 123456789 (1.235E-8). Today I've seen 20 and 28)Īs for the loss in precision, I grant you that MS is listing the SN value to include 20, 30, (more?) digits, but that is NOT how SN is supposed to work, and it STILL rounds values with 'too many' decimals. (if already in SN) rounds the SN to X decimal places (X is not a fixed number in my experience.Depending on many digits (and zeros to the left) the value currently being displayed has, it can either : (2) The F-E button changes how the values are displayed. Maybe you are using it to ball-park a value, but most people would prefer the exact, correct, and complete answer. In my case, one of the things I deal with is counting Photons on the nano-second time scale, as well as all of the timing values that go with that, so precision is pretty important to me. If they didn't care about precision, they would just guestimate it rather than using a calculator.

(1) Asking someone who is using a calculator to compute a value 'Why are you so concerned about precision anyway?' is a pretty non-sensical question. This is just a matter for the part that is converting the number to a string, there should be no precision loss in it? Why are you so concerned about precision anyway? And why would you lose precision by doing this? You can still preserve the same number of significant figures, the overall number would just be longer, although there could be issues with very large exponent. Note: A team member edited this comment for clarity on expected behavior

Add settings for automatic result rounding or display precision to any number of digits to prevent automatic scientific notation to trigger just because result contain lot of digits after decimal point which are not important for userĭevice and Application Information (please complete the following information):.

Disable automatic scientific notation in standard mode calculator at all and add another switch to enable/disable automatic scientific notation in scientific mode if numbers contains more than defined number of zeros after decimal point.

Add another switch to enable/disable automatic scientific notation if number conains more than defined number of zeros after decimal point.

Show scientific notation but also enable F-E switch to indicate scientific notation mode with ability to disable F-E to show number in common decimal format.

Stay in normal decimal format until I press F-E to switch to scientific notation.

If a user manually disables F-E, we should preserve that until the user clears all input or switches modes. You should be able to untoggle the F-E button to force a decimal result.

In Scientific Mode, we should preserve the 'auto-scientfic' behavior, though the F-E switch should be toggled on when we do so.

In Standard Mode, we should disable scientific notation.

Pressing F-E is not changing output format.For example while calculating crypto currencies it is more useful to see 0.000005142857 where I can easily see 514 satoshi price than 5.142857e-6. Sometimes it's more useful and more readable if number stay in common decimal format instead of scientific notation. This automatic scientific notation is also enabled even on standard mode. In scientific mode scientific notation can be enabled by F-E button but can't be disabled if number have more than 2 zeros after decimal point.