Closed prismv closed 5 days ago
I don't think that's a software problem. I just tested on both DM32 and DM42, works perfectly for me.
However, I used to have the problem with my DM42 (only with t
, not p
; I also had a separate problem with the C
key), and it was just that these keys are the closest to the arrow keys, and pushing the arrow key down is sufficient to make the contact with the nearby key become less reliable.
I ended up opening the calculator, readjusted the domes, and fixed the problesm both for C and T keys.
I hope that this works for you. In any case, I cannot reproduce at all.
Thanks. Good to hear that it is not a software bug. Bad for the hardware. Thank you for the hint to your similar problem and mitigation!
Just for completeness: It turned out to be a similar issue as explained in https://forum.swissmicros.com/viewtopic.php?f=18&t=3768. Isolating the 2 screws with Tesa, only low pressure of tightning, and on the other hand some thicker tape between PCB and back helped to bring back P with ▲+[7] reliably. t with ▼+[4] still needs some firmer press of the arrow key and does not work all the time.
▼+[4] and ▲+[7] does not provide transient input of 't' and 'P', respectively, but output of number and erroneous (cursor?) action indicated with a beep.
(tested with current dev branch c6d06a8e)