Dani R. wrote: ↑
Sun Aug 11, 2019 8:00 am
Please excuse my ignorance, Jaco, I have actually not read your current contributions, so I don't know your reasons. I let the triple picture work.
Have a look. I ask the question if Layout1 can stay.
Layout 1: I suspect that '#' and BASE are not the same. #' works for me as a function like RCL. So you have a value and specify the new base in a dialog. I don't know such a functionality, I had always worked with the 'Y' and 'X' registers for such functionalities.
# is a direct input screen like RCL.
BASE is like HP42S BASE and it brings up a menu. BASE includes a sift FN6 for #.
Neither use the stack.
Note: Except for STO and RCL, I can't think of any function that requires parameters as further input.
They use the same direct input screen called TAM, for. RCL & STO, ENG, SCI, etc. and ?????
With RPL they have removed this exception behavior, I think. FIX, ENG etc. are not functions for me, but configuration dialogs. In my personal opinion, I would have liked to avoid functions that require parameters that are not passed via the stack.
I don’t want to change this. This is inherited from WP43S.
Long speech, short sense. If you have '#' you can keep '# as functionality if it already existed on the WP34s. Otherwise I would have liked to have an additional BASE menu in the number pad in layout 1.
# is a direct input, I assume you meant WP43S.
BASE is a menu. And I cannot find a spot in the number pad for it. That is why I don’t like layout 1 anymore. No space for BASE.
Thomas has, I think, reconstructed the functionality of the 16C in the current Free42 pretty completely. But it might also be possible that I'm not concentrated and you find functions of BASE and/or 16C in another menu.
The other bit commands are in other menus. Which????. I don’t think the user interface at the moment can compete with 16C. It needs more work.
Abbreviated: If '#' is a menu it doesn't belong in the second row, if BASE is missing you have to make room.
# belonged there and I can leave # there. I did not destroy #, I added a BASE menu. Maybe there must be a FN to call BASE from #. I like that.
Possible movement; BASE on [f]  and ALPHA on [Sigma+] and send a red label together with the overlays, known procedure...
I am reserving Sigma+ to have a default USER key config to call MyMenu. You can change USER sigma+ to ALPHA
I had already mentioned , [-], [R/S] and [+] movements.
I like them. I will make them if Layout1 stays.
Layout 2: If this variant is a temporary test variant, you can also imagine omitting RTN in it. This means; one function to [g][TAN].
I see Layout2 being very useful and not only temporary.
Do we need Layout1 still?
I have discussed the topic '#' above.
BASE works perfectly here.
Leave HOME at [g] , currently leave ALPHA.FN at [g], move VIEW to [f], would do well there next to SHOW.
To confirm: On Layout2,
move HOME to g,
move a.FN to g,
move VIEW to g[.],
move TEST to f.
That looks very good and puts HOME where I like it. I will do it.
Afterwards you can actually consider to transfer EQN, ADV, timer movements to layout 1. Could work. Then the practical differences between layout 1 and 2 are only COMPLEX and ALPHA.
This brings me to the same question, ie does Layout 1 live or not.
What is currently not finding which function is behind the function on the [g][STO] position in layout 1? Is this a candidate to be omitted or to be replaced with x! ?
Layout1 g[STO] is the complex angle function. Very important to have on direct key.