Thanks to our users for suggestioning new features. This release is just a couple minor bug fixes though. Checkout our download page and stay tuned for the upcoming Linux version! GraphCalc has decided to release the sourcecode to the Windows version of GraphCalc 4. A million thanks to SourceForge for these features:. Recently, we have been flooded with emails from people telling us how much they love GraphCalc.
In January of GraphCalc started as a project to keep us occupied when we were not busy with other commitments. We have been working hard on it, some say too hard, to make a simple and easy to use graphing calculator for windows that is rich in features. Free Online Calculators Here is a list of the best free online calculators that we offer. The curves can be animated, with adjustable framerate and speed.
Experimental data plot and polynomial fit regression. Parametric plot for functions, sequences and parametric equations: the parameter symbol to use is "k".
Plot tangents: they can be moved and resized simply with the mouse. Plot derivatives and antiderviatives. Print the graph, with these options : Choose the size and the position of the graph on the sheet. Print in color or gray-scale. Export on a PDF file. Export to all common image formats png, jpeg, tiff, gif Display a table of values with different options. Navigate on the graph : Select a curve to display the coordinates of its points.
Move the graph. Replaces the content of destination with its absolute value i. Fetches the data byte immediately following the previous CALL statement and puts in into destination. The return address is incremented by one. This is used to pass parameters to subroutines.
Skips several 2-bytes long instructions, according to the value of destination. These instructions are generally BR statements. To push a word on stack, use two PUSH statements. Compares the content of destination to 0 and return result of the comparison into the status byte. These opcodes were intended for use with a GPL expansion card that was never released.
Using them will result in locking the system, since the interpreter doesn't check for the presence of the card before branching to it. Multiplies the content of source and destination and puts the result in destination and the following byte or byte s for DMPY.
Divides the content of destination and the following byte or byte s for DDIV by the content of source. If no overflow occured, the result is placed into destination and the remainder into the next byte s.
The result is placed into destination and compared to zero. The result is places into destination and compared to zero. Performs a bitwise "and" with the contents of source and destination leaving destination unchanged and sets cnd bit if the result is zero. Another way to put it is to say that cnd is set if all bits that are "1" in source are "0" in destination. Shifts the content of destination to the right by the number of bits specified in source, padding the left bits with copies of the sign bit first bit.
Shifts the content of destination to the left by the number of bits specified in source, padding the right bits with 0. Shifts the content of destination to the right by the number of bits specified in source, padding the left bits with 0. Shifts the content of destination to the right by the number of bits specified in source, padding the left bits with the bits deleted to the right. Checks for screen objects coincidence. The COIN statement must be followed by three bytes of data: the first contain the mapping value 0: perfect match, 1: 2 by 2 pixels, 2: 4 by 4 pixels , the next two bytes contain the address of the coincidence table.
For more details and examples on how to use this complicated but usefull instruction, click here. These opcodes were intented for use with a never released GPL expansion board. They should not be used since the interpreter does not check for the presence of the card before branching to it, resulting in lock-ups. Follow these links for more detailed information on sound , CRU handling and cassette tape routines.
Branches to the address found in destination, changing grom base to the value found in source. The return address and current bases are pushed on the subroutine stack to allow returns via the RTGR opcode. Be carefull: source should contain a valid port value: no checking is done and wrong values result in lock-ups! When then opcode FMT is encountered, all the regular GPL opcodes become invalid and are replaced by special opcodes, intended for easy screen handling. These two pointers are updated after each display instruction, in order to point at the next available screen position, but neither can be greater than Increments the column pointer by the content of expression 1 to This may result in incrementing the row pointer by one, if end of line is reached.
Ends a RPTB loop. Normally the operand field should contain the address were to branch, but most of the time this is the address immediately following the RPTB, thus my assembler keeps track of 16 nested RPTB and provides the right address if none was specified.
However, if you would like to branch to a different address, or to nest more than 16 RPTB not very likely to work anyway, since subroutine stack will overflow you should provide the required G address. This screen offset is automatically set to 0 when entering the FMT sub-interpreter. Sets the current row pointer to the byte value contained in expression 0 to Sets the current column pointer to the value contained in expression 0 to The row pointer in not affected.
If the specified column is inferior or equal to the current one, the cursor gets down one line. The FMT sub-interpreter is essentially meant for use in basic mode 32 columns. To provide you with a support for text mode, some pseudo-opcodes have been created. These actually are assembly-time instructions, that are assembled into a serie of regular opcodes. They can only be used with my GPL assembler. This statement is assembled as a ROW and a COL statements, taking into account the fact that there are now 40 characters per line.
0コメント