200ms sounds like a reasonable compromise for now. In the future, perhaps something could be implemented which has a more context dependent delay. For example if you hit the down arrow once, there is very little delay. If you hit down again within x ms there is a larger delay because you are probably holding the key down.
Thanks, Ziba
Thomas Bruederli wrote:
Ziba Scott wrote:
I want to clarify that my question wasn't about changing double-click behavior, it's about reducing/removing the delay for single click behavior. Right now, there is 1/2 a second delay before loading an email preview, presumably to prevent redundant loading of the email when that click was the first of an intended double-click.
I understand your opinion and I suggest to reduce the wait time to about 200ms. The delay is not only important when double-clicking but also when the user scrolls the list with the cursor keys. There's no need to load every message that is highlighted fur just a few ms.
If reducing server load is more important than reducing end-user waiting, it makes sense. At our site, we'd rather use more servers and deliver a more responsive application.
I think we need the best solution for both worlds...
~Thomas
List info: http://lists.roundcube.net/dev/