Why was this calculator created?
This calculator was created to have easy integration into web applications. There are many advanced
standards compliant unless a specific browser is being used (Internet Explorer to be exact). Not only
is it W3C and MSDN (for IE) standards compliant, but the code itself has a consistent format. All
same way. What this calculator aims to do is to work in every condition, be standards compliant, and
when the code is searched through it is very easy to read. Not only that but it is heavily commented
to explain the different functions and features from within. The calculator should work on all
Whats new in 1.2.6? (02/05/2008)
1. Finally I totally rewrote calc_resources\js\keys.js. Keystroke/keycode detection is heavily
simplified. Now it uses a switch statement rather than a bunch of if statements for executing
2. Fixed bug: In Firefox, the '/' key is a shortcut for searching for text. This is a problem
because every time someone divides in Firefox it goes all wierd trying to "search" for text
rather than computing the equation. At the bottom of the functions keydown() and keypress()
in calc_resources\js\keys.js I added a new piece of code that grabs focus away from the search
that way the next key the user types will still interact with the calculator and not the
Firefox search box. Does anyone have a better fix? Please let me know if you do.
Log in to post a comment.