Dani R. wrote: ↑
Sun Aug 04, 2019 4:14 pm
Jaymos wrote: ↑
Sun Aug 04, 2019 12:02 pm
I will scrutinise the opportunities that you mention, and comment when I have done it.
Just to make sure I'm not misunderstood. The current layout works great. I have no problem finding VIEW and SAVE on it. For me, these features are candidates that you could do without if someone actually will creating a second alternative layout. But we still can't know if there are any other pitfalls. And then you might find out that it wasn't worth creating another mock up.
Let me first discuss before I make paper snippets which ones I see as opportunities:
CPX on [g] [SIN] and EXP on [g] [COS]
And from [Sigam+] to [TAN] nowhere a menu.
I love the idea to have no menu items in rows 2 & 3. I do want the top part of the calculator for direct math.
Love the clear thinking.
For example EXP on [g] [CHS], CPX on [g] [x<>y] and STK somewhere close to the programming functions, is mostly only needed for programming. INFO somewhere to go.
[g] [X<>Y] and [g] [CHS] are close to the top, so here I can agree to have CPX and EXP here.
So, STK and INFO go down to the arrows.
And >R and >P go to [g] [SIN} and [g] [COS].
The function SHOW can be anywhere. The function VIEW is, I think, only needed for programming, otherwise you can use R.BR, redundant. Away with it. The function SAVE, as important as it is, can be hidden in a menu, belongs to "SETUP".
I agree with the removal of SAVE. LOAD already sits in the I/O menu, and I see no reason why SAVE cannot sit directly next to LOAD in the menu.In my view, the SAVE position is available if needed.
I disagree with VIEW. I think it is important the VIEW is on a key, and R.BR does not replace it. The problem with R.BR is that you browse to the register, and there are 112 registers. The sequence [f][R.BR]  will immediately navigate to reg 56 at the bottom of the browser screen. The font is small, and there are 11 more registers on the screen, so I still see the need for a simple single register view button. So I believe VIEW stays.
That TIMER and PRGM are functions can be remembered. That means to rethink the positions of the menus in the digits and operator area and to make sure that the functions are grouped.
I definitely need PRGM on a button.
TIMER is debatable and may simply go sit in the I/O menu. So there, possibly, I would say maybe for an available space.
I am quite excited about this proposal. I will think a bit more on the SAVE position. I also find that HOME must be closer, maybe on the down arrow, maybe SHOW must go to the HP42S position [f][.] which means LOOP must go to where HOME was. And maybe FILL comes from the freezer on the side of the field ... let me edit the layout ...