You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Breaking: Add CPLX menu at the previous location of CONV
CPLX menu seemed most convenient on row 1 of the ROOT menu where
the old CONV was located
CONV got pushed to row 2, where the UNIT menu was previously
located
UNIT got pushed to row 3, into an empty slot
the RPN83P home menu row now has exactly the same items as the MATH
menu on the TI-OS:
RPN83P: MATH, NUM, PROB, CPLX
TI-OS: MATH, NUM, CPX, PROB
Support more than 14 digits during edit/input
When more than 14 digits are entered, the left most digits scroll off
to the left, with the left most digit replaced with an ellipsis
character indicates existence of extra digits.
Normal mode:
accepts maximum of 20 digits, which supports entering all 14
digits encoded by the TI-OS floating point number format
Complex mode:
accepts maximum of 41 digits to allow 2 floating point numbers
BASE BIN mode
accepts up to 32 digits, to allow a 32-bit binary number when the WSIZ is 32.
Save and restore app MODE settings independently from the TI-OS settings
decouple the TI-OS MODE settings from the RPN83P MODE settings
the TI-OS MODE settings are saved upon app start, and restored upon
app exit
the app MODE settings are saved and restore independently
for example, it is now possible to set the TI-OS to FIX(2) and DEG,
while setting RPN83P to SCI(4) and RAD and the 2 settings are managed
separately, even though there is only a single set of global OS
settings
Bug Fix: Render 3-digit EE exponents correctly in SHOW mode.
3-digit exponents can only be shown for complex numbers, so the bug
was latent until complex numbers were added
Bug Fix: Fix overflow in rectangular to polar conversion >POL
the built-in TI-OS RToP() function has a bug which throws an
exception when x^2+y^2 becomes >=1e100, which can happen for x
or y as low as 7.07e49.
reimplement using a custom rectToPolar() without the scaling bug