Ok, I also need some opinions. Should the Lanthanides and Actinides be treated like their own little table when navigating? Like, right now, if you're on 68, and press up, it goes to 100. Should it instead go to 113? I'm not sure which is the more intuitive way to handle that.

I mean, I'd probably have to try it out to make a fair opinion, but treating them like their own table sounds slightly more intuitive.

Alright, I had some friends try it out, and the more intuitive way is the visual way, which is to have it not its own little sub-table. So if you're on 56 and press right, you go to 71, and if you're on 5 and press up you go to 100. I've also gotten an input thing in there. It's using Simon's edit string stuff, and it works for now, but I'll want to change it. If you type "23", it tries to go to element 230, instead of element 23. You need to type "023" to get to 23. So that's a little weird. Anyway, here's a screen shot:
I also need to figure out what license I need to release this under. I stole the atoi implementation from SDCC, and it's GPL, and I don't want to GPL all my code, so I'll need to go find a different implementation before release.

Newlib is mostly BSD and some LGPL and if I go with BSD for libfxcg there shouldn't be any issues with statically linking with it. If you need other routines I can look at including them for you, or you could just write your own implementation for use. And even if you do directly use the code from newlib its not an issue as long as you follow the 3-clause BSD license they used.

"Always code as if the person who will maintain your code is a maniac serial killer that knows where you live" -Unknown

"If you've done something right no one will know that you've done anything at all" -Futurama

"Have a nice day, or not, the choice is yours." Tom Steiner

<Michael_V> or create a Borg collective and call it The 83+
<Michael_V> Lower your slide cases and prepare to be silent linked. Memory clears are futile.

A nice little optimized C atoi() implementation might be a fun project for me, not to mention helping you avoid needing the initial zero. Looking great, as expected.

The needing the initial zero isn't a problem with the atio(), it was a problem with the input routine. I've since modified it so that's no longer an issue. Also, Casio has release a new OS version, and it adds support for a new add-in, which is a periodic table. I'll keep working on this one, though, for four reasons:
1) Their add-in requires the OS update, which I'm currently unable to install.
2) Their add-in is 1.71 MB, mine is 142 KB.
3) The code might be useful to people for other things.
4) I want to.
So, at the very least, mine'll be useful if you're low on memory, and as a learning tool. So, once Jonimus makes a build of his thing that has an atoi() implementation is it so I don't need it in my code, I think this thing'll be ready for release

Have your own thoughts to add to this or any other topic? Want to ask a question, offer a suggestion, share your own programs and projects, upload a file to the file archives, get help with calculator and computer programming, or simply chat with like-minded coders and tech and calculator enthusiasts via the site-wide AJAX SAX widget? Registration for a free Cemetech account only takes a minute.