Jaymos wrote: ↑Fri Nov 12, 2021 1:23 pm
That way, there is no spelling issue. Also no human memory issue to remember the spelling. You pick the one you want. Also, the calculator industry is full of variants of writing the same functions including caps. (Also sinh, hsin, hypsin, etc.)
This is precisely the problem I was getting it, or rather, trying to help: Those who only used HPs (say, 41-42 family) might instantly know a priori what naming and casing to use. However, for those coming from other backgrounds (enticing ALL into RPN bliss is the goal, no?
), it's probable they've encountered endless arbitrary variations of abbreviations and capitalizations for such "fundamental" functions.
That's why I'm suggesting there be both "standardization" (built-in functions _all_ be lower-case, whether trig/trans, ln/log, what have you)
PLUS catalog or equivalent "prompting" to handle the case where the poor user's guesses just aren't working out -- we've all been there, and having catalog or auto-completion can be a godsend in those cases. However, catalog alone won't efficiently solve the problem for many users, thus standardization of casing for functions would also be quite useful.
Further, it might be worth making certain very-common or known-conflict-y functions be recognized in any casing (and then corrected to their lower-case form), that would likely be the best UX of all. Lacking that, at least for the functions printed on the keys in upper-case, perhaps provide upper-case "aliases" to the proper lower-case function name? How costly would it be to support "SIN" pointing to "sin", etc. for the few keyboard-printed functions?
Aside, to Walter & co., I'm absolutely gob-smacked at all the hard work put into this, and incredibly appreciative of every bit of it (and as a three-plus-decade embedded/system SWEng, even willing to offer what few spare cycles I can afford, though I'm still spinning up on the source). Please don't misconstrue my comments as being either unappreciative or casual snark, neither is my intention -- if it did come across that way, my apologies.
I'm just running through all the "foolish user" UX scenarios that spring to my mind when I see this stuff discussed, and offering ways to help avoid them from becoming serious pain points /discouragements for new users. I'm fairly new to the DM42, and HP41/42 series in general myself -- more a 16C and very, very novice 48-50 series guy prior. As such, I'm trying to offer the advantages of my "fresh eyes" before they disappear (which, obviously, happens very quickly).
Moreover, why do we still need to press EXIT twice to correct an error?