Messages in this thread | | | Date | Thu, 21 Aug 2003 02:33:45 +0200 | From | Andries Brouwer <> | Subject | Re: Input issues - key down with no key up |
| |
On Thu, Aug 21, 2003 at 01:03:02AM +0100, Jamie Lokier wrote:
> So the decision must be: shall we do the wrong thing for keyboards > which report DOWN only (the key will appear stuck to some programs), > or shall we do the wrong thing for keyboards which report DOWN, no > repeat and then UP, by making it look like the key was released early?
There are many more problems with your synthesized events. Look at your "repeat delay + a bit more". Can you specify how much "a bit more" is?
In times of heavy disk activity we lose interrupts. Indeed, if I copy a CD image or untar a kernel tree my keyboard and mouse are dead for several seconds.
There is no guaranteed "a bit more" within which we will see a keyboard event.
If the only events that are seen are actual events, and on rare occasions we miss an event, that is not so bad. We just hit that key again. But if we synthesize events, then a missed key up causes autorepeat.
In fact I see unwanted autorepeat - maybe once a day suddenly a single keystroke causes three to five identical characters to appear - but I am not sure what mechanism causes this.
Andries
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |