mvent2 wrote:Can you also make pi a bit more accurate, like the Windows version?

3.1415926535897932384626433832795 should be accurate enough

Internally, the calculator uses a precision that's much higher than the displayed value.

It isn't as accurate as Microsoft Calc because it's limited to *double* floats, and 17 numbers with an exponent to +/-308 into a result is quite good.

I just made a better conversion for displaying numbers, now it should look more detailed (show PI=3.1415926535897931).

counting_pine wrote:Just discovered a bug: It doesn't seem to like doing high powers - try 2 ^ 1023.

Not really a bug... max values are:

max = +/-1.79769313486231570e+308

min = +/-2.22507385850720140e-308

so the x^y returns #INF which means infinite. As you said, better precision could be get by rewriting a new floating point engine and do all calculations by hand.

counting_pine wrote:You can't redo operations by pressing "=" multiple times

You are right, but when I wrote the RPN engine I was "inspired" by the engine made for KCalc.

So I wrote something similar for ReactOS calc. This is the explanation.

counting_pine wrote:It won't let you do bitwise ops in decimal mode.

And infact, in my opinion it is a nonsense to do logical operations with numbers that are not integers. So I did it intentionally, by disabling those buttons. However, I'm open to all suggestions, if you think it could be done anyways (how?), we will do it!

counting_pine wrote:The decimal point button is always "," and the display is always "." (Windows gets it from the regional settings). There's a similar situation with the digit grouping.

mmm... yes, I understand. I will try to fix it.

counting_pine wrote:You can't give a decimal point as the first thing in a number; it has to be preceded by a zero.

Found, I will fix it.

Sincerely,

Carlo Bramini