Page 69 of 162

Re: 43S Alternative key layout --> WP43C

Posted: Sun Jan 12, 2020 2:18 pm
by Dani R.
Should be Layout 1B, of course.

UNIT inside CONV, why not.

Concerning aSTR, we have seen on several occasions that it has little to do with ALPHA mode but more with PRGM. So I would not move aSTR away from g[ - ] yet.

So you could keep ALPHA (g[ 4 ]) or ASN (g[ 1 ]) free until a new menu comes up which is still looking for a place. Directly Greek ALPHA mode? I'm just kidding.


EDIT: Or CFG, but does it need this menu directly on a key?

Re: 43S Alternative key layout --> WP43C

Posted: Sun Jan 12, 2020 4:06 pm
by Jaymos
Dani R. wrote:
Sun Jan 12, 2020 2:18 pm
...
So you could keep ALPHA (g[ 4 ]) or ASN (g[ 1 ]) free until a new menu comes up which is still looking for a place.

EDIT: Or CFG, but does it need this menu directly on a key?
My ASN calls my ASN menu. This will be different from 43S’s effort for ASSIGN. I like our way of providing packages for our layout’s different needs, and to also include the top left normal mode key. I may keep both ways if it works.

It may be convenient to move my ASN to g[1] as it is a menu, and put Gert’s ASSIGN on f[1].

I don’t see the need to put CFG on a key real estate. It is quite sufficient to call it from either DISP or MODE.

I will do and publish 1B tonight here, with the menu changes.

Re: 43S Alternative key layout --> WP43C

Posted: Sun Jan 12, 2020 5:10 pm
by Dani R.
Jaymos wrote:
Sun Jan 12, 2020 4:06 pm
Dani R. wrote:
Sun Jan 12, 2020 2:18 pm
...
So you could keep ALPHA (g[ 4 ]) or ASN (g[ 1 ]) free until a new menu comes up which is still looking for a place.

EDIT: Or CFG, but does it need this menu directly on a key?
My ASN calls my ASN menu. This will be different from 43S’s effort for ASSIGN. I like our way of providing packages for our layout’s different needs, and to also include the top left normal mode key. I may keep both ways if it works.

It may be convenient to move my ASN to g[1] as it is a menu, and put Gert’s ASSIGN on f[1].

I don’t see the need to put CFG on a key real estate. It is quite sufficient to call it from either DISP or MODE.

I will do and publish 1B tonight here, with the menu changes.

👍

Re: 43S Alternative key layout --> WP43C

Posted: Mon Jan 13, 2020 1:24 am
by Jaymos
Hi,

Below the progress that I undertook to send through ...

I did the Layout 1B as follows:
Clipboard37.png
Clipboard37.png (187.86 KiB) Viewed 4061 times
This entailed some changes in BASE and CONV menus:
Clipboard38.png
Clipboard38.png (3.6 KiB) Viewed 4061 times
BASE


Clipboard39.png
Clipboard39.png (3.75 KiB) Viewed 4061 times
CONV



The Layout L1B changes are:
  • CHANGED: keys & menus to Layout 1B:
  • Moved d.ms from g[sqrt] to menu MODE to be together with DEG/RAD/…
  • Placed nth-root-of-y on g[sqrt] (key 3, top row)
  • Moved SAVE from g[1] to the I/O menu to be with LOAD etc.
  • Moved ASN menu (43C assign) from f[1] to g[1]
  • Placed ASSIGN (43S future assign) to f[1]
  • Moved UNIT from g[5] to a sub menu inside CONV
  • Placed BASE on g[5]
CHANGED MENU: Menu changes
  • Move MULpi to F4 in menu CONV
  • Removed INTS and BITS menus from BASE as it is easy enough to get them on g[6] and g[x].
  • In BASE menu, re-arranges settings to line f and convert functions to primaries
  • In BASE menu, change >SI to have double functionality [LI <> SI] which changes from real to LI, and if LI to SI| and if SI to LI.
  • In BASE I added the A-F keys, as I find I change between BASE and INTS all the time for that reason.
  • In BASE: I questioned whether [->SI] is needed as there is also >Hex, >BIN … the conclusion it is not needed
  • In BASE menu, Make a BASE, >>LONGINT button. I changed “>SI” to be “R>L<>SI” which is the missing conversion from Real to Longint; then back and forth between Longint to shortint; and if shortint, to longint.
  • In CONV, added >h.ms,


Other issues fixed and added
  • FIXED: Dani reported: Bugs in the glyphs code in softmenu.c
  • FIXED: “ALL 0” does not show the “0”
  • FIXED: Elec formats: if real is used a= is not written.
  • Added sample longint data in registers 10->13, for the 3 cubes = 3 problem.
  • Changed FGDOTS and FGLINE to fgDOTS and fgLINE
  • Changed ELEC2: V/Z to 3V/3Z
  • Changed Pa->mmHg and SB Home - were too long for catalog
    C
  • hanged long items’ catalog text, shorten or use short space. Eg. EM3 with CONV UP
  • FIXED GAP0 not showing.
  • FIXED: Remove settings SH.3t, SH.4s from catalog
  • FIXED: << >>
ADDED special functionality for >R and >P. If a complex number is on X, it rather does RECT or POLAR. Improvement: We need to make >R & >P more intelligent as they are taking up valuable keyboard space. My proposal is the >R must check if X = complex number. If it is complex, the >R will rather call RECT. Same for >P and POLAR. I suggested this months ago. Walter clearly doesn’t want to.

ADDED: Draw diagonal line across the softkey if there is no fnXXXX in items.

Re: 43S Alternative key layout --> WP43C

Posted: Mon Jan 13, 2020 11:48 am
by Dani R.
I'm thinking out loud again. Aren't the functions in CLK more CONV functions? Can "s->year" and "year->s" from UNIT also go to CONV?
So at the moment my impression is that you could do without CLK, but should keep UNIT directly on a key.


The menu ASN could be called CST (CUSTOM), ASSIGN could become ASN again.

Re: 43S Alternative key layout --> WP43C

Posted: Mon Jan 13, 2020 1:12 pm
by Jaymos
Dani R. wrote:
Mon Jan 13, 2020 11:48 am
I'm thinking out loud again. Aren't the functions in CLK more CONV functions? Can "s->year" and "year->s" from UNIT also go to CONV?
They are a combination of setup type and conversion type functions. Conversions on the first page and setup on the second. I agree those year/second conversions could go to CLK. Probably a good place for them. I can move them there.
Dani R. wrote:
Mon Jan 13, 2020 11:48 am
So at the moment my impression is that you could do without CLK, but should keep UNIT directly on a key.
My main reason for moving USER to inside CONV is that every time I wanted UNIT, I typed CONV, maybe being in the habit of the HP42S still. So for 42S legacy it probably is ok for UNIT to be inside CONV.

I would therefore like the UNIT to stay within CONV.
Dani R. wrote:
Mon Jan 13, 2020 11:48 am
The menu ASN could be called CST (CUSTOM), ASSIGN could become ASN again.
I agree with the concept but there may be more complications with layout 2, where we use the physical yellow 'CUSTOM' label to imply 'USER' mode. On Layout2 then, ASN should not be CST because of the confusion with the CUSTOM label which means USER in this case. (Deepl does translate this ok, I checked).

Most practical is probably to have the 43S ASN (or renamed 43S.ASN) as a softkey inside my menu ASN, but that would mean that the menu ASN goes back to a yellow label f[1] where it was in layout 1A.

Re: 43S Alternative key layout --> WP43C

Posted: Mon Jan 13, 2020 2:17 pm
by Dani R.
Jaymos wrote:
Mon Jan 13, 2020 1:12 pm
Dani R. wrote:
Mon Jan 13, 2020 11:48 am
The menu ASN could be called CST (CUSTOM), ASSIGN could become ASN again.
I agree with the concept but there may be more complications with layout 2, where we use the physical yellow 'CUSTOM' label to imply 'USER' mode. On Layout2 then, ASN should not be CST because of the confusion with the CUSTOM label which means USER in this case. (Deepl does translate this ok, I checked).

Most practical is probably to have the 43S ASN (or renamed 43S.ASN) as a softkey inside my menu ASN, but that would mean that the menu ASN goes back to a yellow label f[1] where it was in layout 1A.
Overlook Layout 2; f[ 2 ] is USER, but is labeled CUSTOM.

I have no idea how to rename the additional WP43C softmenu ASN. (CCP? WP43C Custom Packs? Custom Config Pack? CAP? Custom Assign Pack?)

But you noticed, ASSING and ASN next to each other does not look great either.

Re: 43S Alternative key layout --> WP43C

Posted: Tue Jan 14, 2020 12:44 am
by Jaymos
I did the same changes above to Layout2.

SAVE removed from g[1] and is now on the I/O menu.
ASSIGN ASN on [1] as per Layout 1B. The menu is now on blue.
UNIT removed from g[5]. Left BLANK. What can we do there?
INFO g[7] swapped with VIEW g[.] for two reasons: 1. I use the emulator L1B a lot and I frequently get confused on the DM42 with INFO on g[7]. 2. I think that VIEW (View a register) sits nicely next to REGS.V (view many registers).

The red lines left are the changes on the Layout2 on DM42.
The white boxes are where the Layout 1B differs from Layout 2 mods.


On LAYOUT 1B: There is the opportunity to swap g[7] HOME and [g]0] VIEW. It would be nice to have VIEW next to REGS.V.

How are these changes? Comments?
Clipboard40.png
Clipboard40.png (126.43 KiB) Viewed 3992 times

Re: 43S Alternative key layout --> WP43C

Posted: Tue Jan 14, 2020 7:42 pm
by Dani R.
Jaymos wrote:
Tue Jan 14, 2020 12:44 am
UNIT removed from g[5]. Left BLANK.

INFO g[7] swapped with VIEW g[.].


How are these changes? Comments?

For the moment I would retain (additional?) UNIT at g[ 5 ].

VIEW is a function and not a menu. I think that was the reason why VIEW found its position on g[ 0 ] respectively g[ . ]. Probably most likely to be used in programs. Yes, probably REGS.V is more comfortable to use in everyday life.

Re: 43S Alternative key layout --> WP43C

Posted: Tue Jan 14, 2020 9:49 pm
by Jaymos
Dani R. wrote:
Tue Jan 14, 2020 7:42 pm
Jaymos wrote:
Tue Jan 14, 2020 12:44 am
UNIT removed from g[5]. Left BLANK.

INFO g[7] swapped with VIEW g[.].


How are these changes? Comments?

For the moment I would retain (additional?) UNIT at g[ 5 ].

VIEW is a function and not a menu. I think that was the reason why VIEW found its position on g[ 0 ] respectively g[ . ]. Probably most likely to be used in programs. Yes, probably REGS.V is more comfortable to use in everyday life.
To remove a bit confusion, the upcoming version number change will not be Layout 2A, I will make it Layout 42B, so one can remember this is the DM42 version. Layout 1A will become Layout 1B.

UNIT: I will return UNIT to g[5] on L2A. Having UNIT there is better than having it empty, and I need nothing else there.

ASSIGN ASN: Another option is ASN PPP (Pre-Packed Profiles)? One of your previous comments made me think this.
It does not mean it is final. I can easily change.

VIEW/INFO: I now remember about the original placement. But Let me consider the pros and cons again. Maybe we change, maybe we agree to keep it. The facts are: LAYOUT2:
1. REGS.V & FLAGS.V are not menus, but commands for viewers, VIEW is similar and not out of place on g[7] on both layouts.
2. VIEW is used to view named variables, i.e.

Code: Select all

VIEW Test12
and yes you can use REGS.V, but REGS.V has 112 registers plus the named variables, so for quick checks, VIEW is not only for programming, but essential for interactive use. Again it fits nicely on g[7].
3. From a functional point of view, VIEW displays named registers until next keypress, and SHOW shows X until next keypress. Similar, therefore it fits next to SHOW.
4. INFO is a menu and VIEW not. So VIEW does not fit next to CLK, CNST & UNIT. But it does fit with REGS.V and FLAGS.V.

I think after analysing it, it is better to change VIEW/INFO back to where it was. Point 3 is the strongest.



Below the changes as stated above. More comments?


Clipboard45.png
Clipboard45.png (114.99 KiB) Viewed 3942 times
I increased the exposure of the photo, but the extra noise creates a large file. So I had to get the resolution down - so must trouble because I cannot make a screen dump of reliable colour on the Mac screen, for a GTK3 image ... So there is the reason for the crappy quality of the images ...