Yamsoft Calculator Engine / News: Recent posts

Well after an eternity without update, I'm pleased to announce the new version: 1.0.0.6. This new version includes keyboard support, fixed bugs, and a graphing system. Similar to the one found on graphing calculators, this system offers the ability to plot lines and make simple graphs. The new version is coming soon, so, keep watching!

Well as promised last time, I've fixed the very obvious error with the auto-trig function and the page now displays the correct angular measure. Currently, the next features that are anticipated include (but aren't limited to): Computer storage measure conversion, keyboard input, currency conversion, and a "useful equations page". The computer storage measure conversion will be able to convert bits to bytes and the different measures of each including kilo-, mega-, giga-, and tera-. The keyboard input will allow the user to enter numbers and select functions/operators into the main calculator instead of using the virtual-keypad exclusively. The currency conversion page will be more complex and will require more time. In addition, the fact that actual currency values fluctuate poses an obstacle for an "run-offline" program. The "useful equations page" will include a fair-sized list of common equations used to find things like area, volume, density, and perimeter. A better name for this page will most likely be selected before release and any ideas are welcome. Which brings me to the final bit: Should you have any comments, questions, or quirks of any kind that you wish to contact me about directly, please, feel free to contact me through my email account: yamgo@msn.com

It is to my great disappointment that my first news update should be one of warning. Its seems that the latest release, 1.0.0.4 has a defect in the new auto-trig page that never actually converts the radian-units to degrees after calculation if the side "a" and side "b" text-boxes are used. This error will be fixed in the next release, 1.0.0.5. My deepest apologizes go out to those who may run into this problem. The main reason for this and other obvious errors in previous releases is my lack of software testing skills and my lack of inter-release beta testers. If you find any other bugs or if you wish to request a feature, please, feel free to speak-up.