I need input on the HOME concept possible changes:
Some of you gave very good ergonomical type comments when we changed the keyboard around. I need some of that now...
1.
I am considering to make HOME menu a semi permanent feature on screen, i.e. all new menus will pop up on top of the HOME menu, but the last EXIT will not return to a blank screen, but go back to the base menu.
-First Q: Does the idea of a fixed HOME menu (in addition to the g[7] key and 3 x shift) appeal? Will it be better? Is there an improvement to this idea?
2.
I am considering to add a setting in MODE, so you can choose whether you want the base menu to be the HOME menu or to be the custom/user MYMENU.
-Second Q: Does the idea of changing the base menu appeal?
3.
Currently, the alpha input mode defaults to custom/user MyALPHA menu when you enter the input mode.
Currently alpha mode has a "HOME" button called ALPHA on g[0] and on 3 x shift.
I can add a MODE setting to change the default alpha mode menu to ALPHA-HOME instead of MyALPHA.
-Third Q: Does this appeal? Comments or better ideas please.
WP43 Alternative key layout --> C43
Re: 43S Alternative key layout --> WP43C
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
Re: 43S Alternative key layout --> WP43C
A1: Honestly, it didn't immediately sound appealing, but it might grow on me.
I would like to see some examples, and learn a bit more about the motivation. An option to switch it off wouldn't hurt either, if you could easily create that. That would give us the possibility to give you feedback based on actual experience, and in the end, users can opt in or out as they wish.
A2: Yes!
A3: Yes!
What is the metric tensor in imperial units?
Re: 43S Alternative key layout --> WP43C
Let me answer your questions a little differently. It is the intention of WP43S to display the two user menus MyMenu and Myα as default, if firstly something is assigned and secondly no other menu is called. In WP43S/C you can see this e.g. by the fact that in normal mode no menu is visible if no other menu is called and in alpha mode a menu with the assignment 'ä, 'ö', 'ü' etc. is simulated.
Now to your questions. It is always good to have freedom of choice. I got used to the "blank screen". I can imagine that in the emulator in normal mode I will like to have "blank screen", but on the DM42-WP43C e.g. MyMenu, when all EXIT are finished.
1. / 2. I would like to be able to choose between "blank screen", MyMenu and HOME for the base menu.
In alpha mode I prefer your ALPHA-HOME, no matter if emulator or DM42-WP43C.
(This brings me to the next point. In ALPHA-HOME you can call Myα from 'F1'. I don't see where you can call MyMenu in normal mode in HOME. Since you hardly need HOME in alpha mode, you can remove Myα from HOME.)
3. I would like to be able to choose between "blank screen", Myα and ALPHA-HOME for the base menu in alpha mode.
"blank screen" could also be something like DM42.
Now to your questions. It is always good to have freedom of choice. I got used to the "blank screen". I can imagine that in the emulator in normal mode I will like to have "blank screen", but on the DM42-WP43C e.g. MyMenu, when all EXIT are finished.
1. / 2. I would like to be able to choose between "blank screen", MyMenu and HOME for the base menu.
In alpha mode I prefer your ALPHA-HOME, no matter if emulator or DM42-WP43C.
(This brings me to the next point. In ALPHA-HOME you can call Myα from 'F1'. I don't see where you can call MyMenu in normal mode in HOME. Since you hardly need HOME in alpha mode, you can remove Myα from HOME.)
3. I would like to be able to choose between "blank screen", Myα and ALPHA-HOME for the base menu in alpha mode.
"blank screen" could also be something like DM42.
C47(DM42) SN:00032 WP43 SN:00016
https://47calc.com
https://47calc.com
Re: 43S Alternative key layout --> WP43C
Thanks for the comments guys.
The long and the short is yes, you want all in settable options .... I could have guessed I am putting those options in there, to help us decide what we want. It needs a bit more time though.
Interesting, Guenter actually got the WP43C as a talk topic on the HHC. See the schedule: https://hhuc.us/2019/schedule.htm. Tell us what happened yesterday!
I also started to put in some constants, i.e. operator a (120 degree unity vector) and j (90 degree unity vector) (as used by EE's) when shifting vectors through 120 degrees and 90 degrees - useful to have the standard vector on f[F1]. I'm fiddling around with some vector formulas I often need - maybe it will end as EE package doing sequence components, delta/wye conversions, etc - just exploring options. Maybe I just ditch it.
I integrated this weekend's significant WP43S upgrades into the WP43C - but I am not ready yet to publish the emulators and firmware. Will do in a few days.
The long and the short is yes, you want all in settable options .... I could have guessed I am putting those options in there, to help us decide what we want. It needs a bit more time though.
Interesting, Guenter actually got the WP43C as a talk topic on the HHC. See the schedule: https://hhuc.us/2019/schedule.htm. Tell us what happened yesterday!
I also started to put in some constants, i.e. operator a (120 degree unity vector) and j (90 degree unity vector) (as used by EE's) when shifting vectors through 120 degrees and 90 degrees - useful to have the standard vector on f[F1]. I'm fiddling around with some vector formulas I often need - maybe it will end as EE package doing sequence components, delta/wye conversions, etc - just exploring options. Maybe I just ditch it.
I integrated this weekend's significant WP43S upgrades into the WP43C - but I am not ready yet to publish the emulators and firmware. Will do in a few days.
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
Re: 43S Alternative key layout --> WP43C
We were a little bit ahead of time, therefor I quickly hacked some words together to give an overview on the fly. Although I sometimes mixed the WP43C and the WP34S it finally became clear, what I was talking about. A number of people approached me afterwards for some more in depth explanations.Jaymos wrote: ↑Sun Sep 22, 2019 8:24 pm
Interesting, Guenter actually got the WP43C as a talk topic on the HHC. See the schedule: https://hhuc.us/2019/schedule.htm. Tell us what happened yesterday!
Günter, from the HHC2019
Günter
DM42 SN:00004 and SN:00184 -- DM41X SN:00013 and SN:00955
DM42 SN:00004 and SN:00184 -- DM41X SN:00013 and SN:00955
Re: 43S Alternative key layout --> WP43C
DM42 issues ... still persist. I've been holding back on purchasing at least 2 DM42s (one for me, and one for my enthusiastic, tech minded 16 year old) until I was confident that those pesky keyboard issues had finally been resolved. So, you can imagine how deflated I felt when I read the following post:
PS ... makes one wonder how many others out there (world-wide) are also reluctantly sitting on their money, really wanting to purchase, but ...
Is this ever going to be resolved ...?jaykstone wrote: ↑Wed Sep 25, 2019 5:14 pmHas anyone tried replacing the dome switches?
I purchased a DM42 and received it last weekend. I immediately loved everything about it except the keys. Keys were hard to press, and many of them could click without registering unless i pressed harder after the click. I decided I was intent on keeping this calculator and really did not want to send it back.
First I tried the gentile key bending. this did reduce the required force, but keys could still click and not register. Next I put a dab of UV curable plastic on center of each dome. this helped on some keys, but was too thick on others. I gently ground down the added plastic until all keys worked. This was better than when I started, but I would still miss some keystrokes where a click was felt but the press did not register.
I took the DM42 to work for a day and decided the keyboard was just causing too many mistakes.
I peeled back the sheet of domes, and everything looked perfectly clean. I cleaned with Isopropyl alcohol anyway, and still no change.
Finally I decided to remove the plastic I had added on and replace the snap domes. first I peeled off the plastic bits I had added with tweezers. The only domes I had on hand was some 6mm domes I was able to salvage from some scrap keypads at work, but it looked like they might work even though they are smaller. I carefully removed half of the original 8mm domes (from top half of keyboard)and replaced them with the domes I had on hand, carefully centering each one and sticking it on the plastic sheet. Upon re-assembly, all of the keys with the new domes worked perfectly. I could not get a key to click without registering. I repeated this on the remaining keys with the same result. Now every key works great.
Has anyone else tried this? I suspect there may be other domes (from Snaptron etc) to consider from a feel perspective, but based on my results it seems like replacing the domes could be promising. Any thoughts?
Jay
PS ... makes one wonder how many others out there (world-wide) are also reluctantly sitting on their money, really wanting to purchase, but ...
D A MacDonald
Mar Eng, Designer, CANADA
HP35, HP41C, HP28S, HP35s. PC: HP15C, Free42, WP31S, WP34S
(Operators Right in bold)
"It is not the strongest or most intelligent who will survive but those who can best manage change ..." Darwin
Mar Eng, Designer, CANADA
HP35, HP41C, HP28S, HP35s. PC: HP15C, Free42, WP31S, WP34S
(Operators Right in bold)
"It is not the strongest or most intelligent who will survive but those who can best manage change ..." Darwin
Re: 43S Alternative key layout --> WP43C
Good question. I had the same problem with my beta model, and fixed it using replacement domes + carefully bending the keys. Now I am super happy with the feel.inautilus wrote: ↑Wed Sep 25, 2019 6:55 pmDM42 issues ... still persist. I've been holding back on purchasing at least 2 DM42s (one for me, and one for my enthusiastic, tech minded 16 year old) until I was confident that those pesky keyboard issues had finally been resolved. So, you can imagine how deflated I felt when I read the following post:
[...]
Is this ever going to be resolved ...?
PS ... makes one wonder how many others out there (world-wide) are also reluctantly sitting on their money, really wanting to purchase, but ...
The solution to the problem is certainly within reach, and there is something un-Swiss about not applying it...
What is the metric tensor in imperial units?
Re: 43S Alternative key layout --> WP43C
HP42S COMPLEX compatibility
I am considering to add a config flag to optionally force COMPLEX compatibility for 42S. Is this complex entry a problem for anyone else?
The issue is that on 43S, you either do
1 CC 2 EXIT (or 1 CC 2 ENTER) or
1 ENTER 2 EXIT CC
On 42S you do:
1 ENTER 2 CC or
1 ENTER 2 EXIT CC
Both are similar, but sufficiently different to cause finger trouble. I very frequently on the 43C do:
1 ENTER 2 COMPLEX which would have been good on the 42S but which enters 1 and starts a new complex number starting with 2. I don't like that and I can't seem to shake the habit.
I think a wrapper function with optional flag to force EXIT upon calling COMPLEX will be a simple fix.
When COMPLEX (actually CC) is called to terminate entry first (EXIT), will mean that the sequence 1 ENTER 2 CC will always result in the equivalent of 1 ENTER 2 EXIT CC. This concept is it will then always do 42S style complex input. I will check the code maybe it is more complicated.
I am considering to add a config flag to optionally force COMPLEX compatibility for 42S. Is this complex entry a problem for anyone else?
The issue is that on 43S, you either do
1 CC 2 EXIT (or 1 CC 2 ENTER) or
1 ENTER 2 EXIT CC
On 42S you do:
1 ENTER 2 CC or
1 ENTER 2 EXIT CC
Both are similar, but sufficiently different to cause finger trouble. I very frequently on the 43C do:
1 ENTER 2 COMPLEX which would have been good on the 42S but which enters 1 and starts a new complex number starting with 2. I don't like that and I can't seem to shake the habit.
I think a wrapper function with optional flag to force EXIT upon calling COMPLEX will be a simple fix.
When COMPLEX (actually CC) is called to terminate entry first (EXIT), will mean that the sequence 1 ENTER 2 CC will always result in the equivalent of 1 ENTER 2 EXIT CC. This concept is it will then always do 42S style complex input. I will check the code maybe it is more complicated.
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
Re: 43S Alternative key layout --> WP43C
I think the main reason for having the 43S style "1 [CC] 2 [op]" (where "[op]" is any operation that terminates number entry) is that it only loses the original T register contents, compared to "1 [ENTER] 2 [EXIT] [CC]" which loses the original T and Z register contents (assuming a 4-level stack).Jaymos wrote: ↑Thu Sep 26, 2019 12:00 amHP42S COMPLEX compatibility
I am considering to add a config flag to optionally force COMPLEX compatibility for 42S. Is this complex entry a problem for anyone else?
The issue is that on 43S, you either do
1 CC 2 EXIT (or 1 CC 2 ENTER) or
1 ENTER 2 EXIT CC
On 42S you do:
1 ENTER 2 CC or
1 ENTER 2 EXIT CC
Both are similar, but sufficiently different to cause finger trouble. I very frequently on the 43C do:
1 ENTER 2 COMPLEX which would have been good on the 42S but which enters 1 and starts a new complex number starting with 2. I don't like that and I can't seem to shake the habit.
I think a wrapper function with optional flag to force EXIT upon calling COMPLEX will be a simple fix.
When COMPLEX (actually CC) is called to terminate entry first (EXIT), will mean that the sequence 1 ENTER 2 CC will always result in the equivalent of 1 ENTER 2 EXIT CC. This concept is it will then always do 42S style complex input. I will check the code maybe it is more complicated.
My preference would be to have both [CC] and [COMPLEX] as separate entities (although I'm not fussy about the names). [CC] would be just a number key (separating the real and imaginary parts of number entry), whereas [COMPLEX] would be an operation like on the 42S. So you could do:
1 [ENTER] 2 [COMPLEX] (42S style), or
1 [CC] 2 [op] (43S style).
This leads to the following unusual sequences:
1 [CC] [op] (enters a complex number 1.+i*0.)
[E] [CC] [op] (enters a complex number 1.+i*0.)
[CC] 1 [op] (enters a complex number 0.+i*1.)
[CC] [E] [op] (enters a complex number 0.+i*1.)
[E] [CC] [E] [op] (enters a complex number 1.+i*1.)
[CC] [op] (enters a complex number 0.+i*0.)
1 [CC] 2 [COMPLEX] (enters a complex number 1.+i*2. and then splits it into two reals Y=1., X=2.)
[CC] [COMPLEX] (enters a complex number 0.+i*0. and then splits it into two reals Y=0., X=0.)
Re: 43S Alternative key layout --> WP43C
In summary, as I understand, you propose one step further, i.e. to rather optionally prevent CC from having 42S compatibility, and also to introduce a new command COMPLEX, which only has 42S compatibility.
I am liking your idea of a separate COMPLEX function, for the reason that I try keep the existing commands (CC) standard for the purposes of future programming complications.
I can do this without flags by simply adding 2 wrappers to CC, one called COMPLEX for strict 42S compatibility and another called say CC1. We would use USER to replace the yellow COMPLEX with either CC or CC1. And if you need both, replace top left Σ+ with CC1.
Just to be clear: currently, CC operation already includes 42S style, i.e. when typing CC with no preceding number, it already does 42S style on X and Y, and terminates. I would need to block that.
Currently the E functionality does not work as you show and I don’t intend to change it. Only after starting numerical input mode (NIM) with a number (not E), CC changes input to imag.
All your examples starting with CC does currently not work due to the above. This would need the CC1 mod to not take X and Y and terminate.
Currently:
1 [CC] [op] (enters a complex number 1.+i*0.) renders 1+i*1
[E] [CC] [op] (enters a complex number 1.+i*0.) Does not terminate entry once E is opened. Expecting exponent entry.
[CC] 1 [op] (enters a complex number 0.+i*1.) Not. Takes X Y and terminates after CC.
[CC] [E] [op] (enters a complex number 0.+i*1.) Not. Takes X Y and terminates after CC.
[E] [CC] [E] [op] (enters a complex number 1.+i*1.) Not. Does not work. Does not proceed with CC once E is opened.
[CC] [op] (enters a complex number 0.+i*0.) Not. CC works on x and y 42S style.
1 [CC] 2 [COMPLEX] (enters a complex number 1.+i*2. and then splits it into two reals Y=1., X=2.) Would work once new COMPLEX is done.
[CC] [COMPLEX] (enters a complex number 0.+i*0. and then splits it into two reals Y=0., X=0.) Not. CC works on x and y 42S style.
I am liking your idea of a separate COMPLEX function, for the reason that I try keep the existing commands (CC) standard for the purposes of future programming complications.
I can do this without flags by simply adding 2 wrappers to CC, one called COMPLEX for strict 42S compatibility and another called say CC1. We would use USER to replace the yellow COMPLEX with either CC or CC1. And if you need both, replace top left Σ+ with CC1.
Just to be clear: currently, CC operation already includes 42S style, i.e. when typing CC with no preceding number, it already does 42S style on X and Y, and terminates. I would need to block that.
Currently the E functionality does not work as you show and I don’t intend to change it. Only after starting numerical input mode (NIM) with a number (not E), CC changes input to imag.
All your examples starting with CC does currently not work due to the above. This would need the CC1 mod to not take X and Y and terminate.
Currently:
1 [CC] [op] (enters a complex number 1.+i*0.) renders 1+i*1
[E] [CC] [op] (enters a complex number 1.+i*0.) Does not terminate entry once E is opened. Expecting exponent entry.
[CC] 1 [op] (enters a complex number 0.+i*1.) Not. Takes X Y and terminates after CC.
[CC] [E] [op] (enters a complex number 0.+i*1.) Not. Takes X Y and terminates after CC.
[E] [CC] [E] [op] (enters a complex number 1.+i*1.) Not. Does not work. Does not proceed with CC once E is opened.
[CC] [op] (enters a complex number 0.+i*0.) Not. CC works on x and y 42S style.
1 [CC] 2 [COMPLEX] (enters a complex number 1.+i*2. and then splits it into two reals Y=1., X=2.) Would work once new COMPLEX is done.
[CC] [COMPLEX] (enters a complex number 0.+i*0. and then splits it into two reals Y=0., X=0.) Not. CC works on x and y 42S style.
Jaco Mostert
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.
Elec Eng, South Africa
https://47calc.com C47 (s/n 03818 & 06199), WP43 (0015). In box: HP42S, HP32Sii, WP34S&C, HP28C, HP35s, EL-506P, EL-W506, PB700; ex: FX702P, 11C, HP67 & HP85; iOS: 42s Byron, Free42+, WP31S/34S, HCalc.