On 05/23/2016 03:19 PM, Gerd Hoffmann wrote:
Limits the rate kbd events from the vnc server are forwarded to the
guest, so input devices which are typically low-bandwidth can keep
up even on bulky input.
Signed-off-by: Gerd Hoffmann
---
ui/vnc.c | 13 +++--
Hi,
> > +key_delay_ms = qemu_opt_get_number(opts, "key-delay-ms", 1);
>
> Why the default value is 1 and not 0?
> (Are there some impacts on the "qemu_input_event_send_key_delay(0);" you
> replace above?)
I think it makes sense to have a delay by default, so the guest is
scheduled to run
On 23/05/2016 15:19, Gerd Hoffmann wrote:
> Limits the rate kbd events from the vnc server are forwarded to the
> guest, so input devices which are typically low-bandwidth can keep
> up even on bulky input.
>
> Signed-off-by: Gerd Hoffmann
> ---
> ui/vnc.c | 13
On 23/05/2016 15:19, Gerd Hoffmann wrote:
> Limits the rate kbd events from the vnc server are forwarded to the
> guest, so input devices which are typically low-bandwidth can keep
> up even on bulky input.
>
> Signed-off-by: Gerd Hoffmann
This patch fixes also a problem
Limits the rate kbd events from the vnc server are forwarded to the
guest, so input devices which are typically low-bandwidth can keep
up even on bulky input.
Signed-off-by: Gerd Hoffmann
---
ui/vnc.c | 13 +++--
ui/vnc.h | 1 +
2 files changed, 12 insertions(+), 2