Just an observation:
In non-programming mode I can use a "long button press" to figure out that, for example, RTNY is the abbreviation of RTNYES.
I cannot use the same method to figure out that RTNE is the abbreviation of RTNERR (because I immediately get Restricted Operation).
New Free42 utilities: inconsistent (?) behaviour at long button press
- Stefan Karlsson
- Posts: 26
- Joined: Thu Apr 04, 2019 10:26 pm
-
- Posts: 1100
- Joined: Tue May 02, 2017 5:48 pm
- Location: Netherlands
- Contact:
Re: New Free42 utilities: inconsistent (?) behaviour at long button press
The long press trick only works with functions with no parameters. For functions with parameters, the calculator goes into command entry mode immediately, displaying the function name and prompting for the parameter... unless it's a PRGM-only function and you're doing it in RUN mode.
The same thing happens when you press INPUT or LBL in run mode.
There are some inconsistencies in what causes the Restricted Operation error and when exactly it is displayed, but I felt I was following established precedent in how I handled it with RTNERR.
The same thing happens when you press INPUT or LBL in run mode.
There are some inconsistencies in what causes the Restricted Operation error and when exactly it is displayed, but I felt I was following established precedent in how I handled it with RTNERR.
- Stefan Karlsson
- Posts: 26
- Joined: Thu Apr 04, 2019 10:26 pm
Re: New Free42 utilities: inconsistent (?) behaviour at long button press
I see; I had a feeling that the "inconsistency" was in reality a lack in my understanding of the machine.