pondlife wrote:
As I see it, the problem is that list entries are never voiced until the button is released (and 0.25 of a second has passed).

If list.c is modified so that first and last entries are voiced immediately, I don't think we'd need this beep, right?
That's more or less what it sounds like to me. It seems like a bug to me that the last entry in either direction isn't voiced as long as the button is held down.

Reply via email to