https://bugs.kde.org/show_bug.cgi?id=500690
--- Comment #11 from Philipp Maierhöfer <maiphi.pub...@gmx.net> --- We've been discussing 5 different issue here. Let me summarize to avoid confusion: 1. Translation mistake ms = min in en_GB. 2. kaccess crash (https://bugs.kde.org/show_bug.cgi?id=500326). 3. Slow keys not working on Wayland (https://bugs.kde.org/show_bug.cgi?id=490826). 4. Allowed value range doesn't cover all use cases. 5. Misbehaving spin boxes: when a value is typed in, the "apply" button doesn't become available. Using the arrow buttons reset typed in values to 100. Can anyone reproduce this? To point 4: As I understand it, slow keys essentially applies a "defer" debounce algorithm, bounce keys applies an "eager" algorithm. Maybe this is useful with large delays as accessibility feature for people with certain medical conditions. To use it as software debouncing of a keyboard that has problems with key chatter, 5 ms delay is a common value (see https://docs.qmk.fm/feature_debounce_type). The better place to do this is the keyboard firmware, but if that is not possible, software debouncing in the OS is very useful. I configured this quite some time ago and everything was working fine for me until a few days ago when I switched this particular machine to Wayland. -- You are receiving this mail because: You are watching all bug changes.
