Molencalc - a simple, engineer-friendly calculator

For a long while, i’ve wanted a little calculator to sit by my electronics bench and help out with the little calculations that come up - in a way that makes it not matter if “nF” should be “e-9” or “e-12”

So when PicoCalc came out, i knew i had to grab one and build it :smiley:

And here it is! GitHub - TheRealMolen/molencalc: an engineering calculator for picocalc

There’s still plenty i’d like to add – complex numbers, graphing, etc.

But i reckon it’s pretty handy the way it is already :slight_smile:

It’s based on the picocalc-text-starter (thanks @BlairLeduc!), and i’ve also built a little SDL-based “emulator”/testbed for faster iteration: GitHub - TheRealMolen/mcalc: graphical calculator for picocalc

11 Likes

Just released v15, with nice inline graphs :slight_smile:

3 Likes

This is great - the syntax of defining functions with f: and graphing with :g is new to me - is there documentation for this? Thank you very much.

Hey Bryn :slight_smile:

The syntax was originally a bit “vi-like” because it made the parsing a bit simpler, but i’ve just pushed v16 which removes the : from the beginnings of commands, and adds a much better help command.

I’ve also expanded the README so it now has some instructions on how to use things :slight_smile:

Please lmk if they’re helpful, or if there’s more clarity needed.

cheers – molen

This is VERY helpful, thanks! I was looking for a “help” and now you have it - great.

And I think the move to simpler syntax is also helpful (eg: “g” instead of “:g”), so to that end could I suggest that when defining a function, the “->” could be eliminated? Or perhaps replaced with “,” as in the graph command. That is, you are defining “f:” and the first argument is the “x” and the second arg is the y value as a function of that x, which in the graph command is delimited by a comma. Just a thought (I’m slow typing with that little keyboard!)

Also, and unusual thing. I tried “small” and found the lowercase “g” has an unusual graphical glitch. Almost like it is g prime g’ somehow.

Should these comments be made in your git project somehow, or is it okay to post here?

Thanks again, I will be using this.

I’m glad that was helpful :smiling_face:

I know what you mean about the syntax being fiddly to type - I often end up pressing z instead of SHIFT… Let me have a think on how to improve that!

Funnily enough I noticed that little glitch with the small g last night too. I need to dig through the binary data and find a bit to flip I think :grin:

1 Like

ok - i think v17 should hopefully make life a bit easier

You need to use the SHIFT key much less now (only really for + and *, and for the < when specifying axis ranges). You can use the [ and ] brackets instead of the ( ) ones.

Function and variable definitions are much simpler and are unified now - it’s just

> f[x]=sinc[x]
> theta = 3pi/2