thanks Bob!rprosperi wrote: ↑Wed Feb 06, 2019 2:47 amI'm not 100% why folks are advocating these alternates (there seem to be multiple points being made) but the main difference is that [Enter] disables stack-lift, so the next thing entered replaces X without pushing the stack up, while the other methods terminate entry with stack lift enabled. To me, there are corner cases where this can make a difference, but typically it's not important. The usual reason folks pursue this is if they learned RPL before RPN, where all terminated entries always enable stack lift. These tricks better simulate the behavior of RPL.
Keyboard debouncing
Re: Keyboard debouncing
Cambridge, UK
41CL 12/15C DM15/16 71B 17B/BII/bII+ 28S 42S/DM42 48GX 50g 35s 30b/WP34S Prime G2
& Casios, Rockwell 18R
41CL 12/15C DM15/16 71B 17B/BII/bII+ 28S 42S/DM42 48GX 50g 35s 30b/WP34S Prime G2
& Casios, Rockwell 18R

Re: Keyboard debouncing
One more reason why WP calculators stick to RPN.

IIRC, far less people complained about ENTER at times when one-line displays were standard. More than two output lines seem to add confusion instead of enlightenment. Just an observation.

DM42 SN: 00041 --- Follower of Platon.
HP-35, HP-45, ..., HP-50, WP 34S, WP 31S, DM16L
HP-35, HP-45, ..., HP-50, WP 34S, WP 31S, DM16L
Re: Keyboard debouncing
I've noticed this too Walter, quite weird and unexpected; it would seem that being able to view more of the stack would provide confirmation of what one has presumably understood all along. But again, folks that started on RPL have always seen the entire stack, plus never needed to learn the subtleties of Stack-lift enable, -disable, etc. I suppose the lesson here is that with only 1-level visible, one had to spend more time thinking about what was where in the stack, rather than directly observing it.
--bob p
DM42: β00071 & 00282
DM42: β00071 & 00282
Re: Keyboard debouncing
Yeah, thinking often helps.rprosperi wrote: ↑Wed Feb 06, 2019 9:31 pmI've noticed this too Walter, quite weird and unexpected; it would seem that being able to view more of the stack would provide confirmation of what one has presumably understood all along. But again, folks that started on RPL have always seen the entire stack, plus never needed to learn the subtleties of Stack-lift enable, -disable, etc. I suppose the lesson here is that with only 1-level visible, one had to spend more time thinking about what was where in the stack, rather than directly observing it.

DM42 SN: 00041 --- Follower of Platon.
HP-35, HP-45, ..., HP-50, WP 34S, WP 31S, DM16L
HP-35, HP-45, ..., HP-50, WP 34S, WP 31S, DM16L
Re: Keyboard debouncing
I'm using the latest firmware revision DMCP_3.14 (A new version gets a chance!). I've been using the calculator for a few hours and I think the keyboard reading has improved. In this time I haven't observed repeated keystrokes. Is it a coincidence or have you improved the keyboard debounce?
In my calculator repeated keystrokes were especially annoying and make it unusable.
Let's see if it's true!
In my calculator repeated keystrokes were especially annoying and make it unusable.
Let's see if it's true!
-
- Posts: 529
- Joined: Wed May 03, 2017 5:46 pm
- Location: Malone, NY USA
Re: Keyboard debouncing
I try to avoid that whenever possible.

Tom L
My father was a man of the cloth. He was a tailor.
DM42 SN: 00025 (Beta)
SN: 00221 (Shipping)
My father was a man of the cloth. He was a tailor.
DM42 SN: 00025 (Beta)
SN: 00221 (Shipping)
Re: Keyboard debouncing
The announcement mentions:cesar wrote: ↑Tue Jul 16, 2019 10:02 amI'm using the latest firmware revision DMCP_3.14 (A new version gets a chance!). I've been using the calculator for a few hours and I think the keyboard reading has improved. In this time I haven't observed repeated keystrokes. Is it a coincidence or have you improved the keyboard debounce?
In my calculator repeated keystrokes were especially annoying and make it unusable.
Let's see if it's true!
- Keyboard handling completely reworked
which sounds good.
Cambridge, UK
41CL 12/15C DM15/16 71B 17B/BII/bII+ 28S 42S/DM42 48GX 50g 35s 30b/WP34S Prime G2
& Casios, Rockwell 18R
41CL 12/15C DM15/16 71B 17B/BII/bII+ 28S 42S/DM42 48GX 50g 35s 30b/WP34S Prime G2
& Casios, Rockwell 18R

-
- Posts: 619
- Joined: Tue May 02, 2017 3:48 pm
- Contact:
Re: Keyboard debouncing
If you were to actually dial those numbers, I'm sure you would remember them, but if you're just tapping names in your contact list, and letting the phone do the dialing for you, there's not much to cause the numbers to stick in your brain. And there's even less if the phone doesn't even show the numbers on the screen while it's dialing them.toml_12953 wrote: ↑Tue Jul 16, 2019 12:07 pmI do note that since I can now store all my contact information in my phone, my ability to remember phone numbers has decreased markedly. Old age has nothing to do with it (does it?)
As a counter-example, I've heard the claim numerous times that GPS is causing people to lose the ability to find their way without help. In my experience, this is not the case. For example, about three years ago, I moved to a new town. The area was completely unfamiliar to me, and in the beginning, I used the navigation app on my phone everywhere I went (except to go grocery shopping — I live right behind a shopping center so the grocery store is really easy to find

Re: Keyboard debouncing
But... but... you'd previously developed spatial awareness (ie can read a map and visualise the locale). Many now use GPS when repeating the same trip.Thomas Okken wrote: ↑Wed Jul 17, 2019 12:43 am... But as time passed, I found myself using the GPS less and less, and by now, I don't use it at all anymore. I never made an effort to memorize all those routes and areas; they just gradually stuck.
Re: Keyboard debouncing
I installed the latest firmware and seem to have no more bouncing issues... so far! Others ?