H2X wrote: ↑
Sat Aug 24, 2019 8:13 pm
Jaymos wrote: ↑
Sat Aug 24, 2019 7:42 pm
H2X wrote: ↑
Sat Aug 24, 2019 7:25 pm
Does "character" suggest single character manipulations?
Good question: my thoughts were that it refers to character based
manipulations, including multiple characters like shifting of a string of characters for example.
I understand your thinking.
I can't help noticing that "string of characters" snuck itself into that last sentence of yours, though...
What are the options though? I copied the suggestions in the posts above:
would be ideal if I can fit it in the space.
CR.FN is too vague and does not remind of character.
CS.FN also is far from intuitive.
may be effective, even if there is no FN.
STR.FN for L1A
TX.FN which can work
ST.FN which is confusing due to STK
T.FN may also work.
or TXT.FN or STR.FN (if it fits), but not STR which is too close to STK.
S.FN rarely used, and then by the people who use P.FN also.
A.FN maybe the big A is enough to establish the distance to ALPHA.
STR might not be a good name, since STK already exists
The facts for .FN functions are:
- P.FN (is on the same button as PRGM, conveniently differentiating from PRGM (or P/R originally)).
- X.FN (short form for extra mathematical functions)
- a.FN (alpha functions, differentiating from a which is on the same button)
- a.FN includes character and string manipulation.
- The FN in P.FN and a.FN are to avoid confusion and to be unique. There is a FN in X.FN because it is short for EXTRA FUNCTIONS.
- Many other menus have functions, but are not called .FN because there is no reason.
There is no confusion for a.FN if we remove it from the same button as alpha, and if the label word is changed. My point is it needs no .FN.
Then we have 5 letters, and we don't need to waste 3 letters on .FN.
The a.FN menu is for 7 STRING AND 1 CHARACTER manipulation functions. So, in short, we have with STRING MANIPULATION. Therefore, the apt work to use is STRING, which is as H2X recently said, Dani earlier, and myself this evening: we are dealing with strings.
Options therefore are:
STRING (too long)
STR (too much like STK)
STRNG (can work)
STRG (can work)
I choose STRNG and the result looks like this. Any objections to the summary or the logic?
See implementation on Layout 1A.