From: Dave Mielke <dave@mielke.cc>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/4] input: add support for kbd delays
Date: Mon, 2 Jun 2014 08:59:30 -0400 [thread overview]
Message-ID: <20140602125930.GG10889@beta.private.mielke.cc> (raw)
In-Reply-To: <1401708518-2071-1-git-send-email-kraxel@redhat.com>
[quoted lines by Gerd Hoffmann on 2014/06/02 at 13:28 +0200]
Hi:
>Little series of four input patches.
Yes, it all seems to work correctly, now, with these four patches applied.
Perhaps there should be a common constant that all the delay calls use. Maybe
even a variable which defaults to 10 and is set by something like the -k delay=
in my patch. That'd allow users to modify it if it isn't quite right in some
other circumstance, as well as to reduce it to 0 if they perceive a need to do
so.
It might be a good idea to introduce an intermediate call which doesn't have a
"length of delay" argument, which then calls the current function with the
desired value.
These are, of course, cosmetic suggestions. The code as it now stands dodes
work.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/
EMail: dave@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.com/
prev parent reply other threads:[~2014-06-02 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 11:28 [Qemu-devel] [PATCH v2 0/4] input: add support for kbd delays Gerd Hoffmann
2014-06-02 11:28 ` [Qemu-devel] [PATCH 1/4] " Gerd Hoffmann
2014-06-02 11:28 ` [Qemu-devel] [PATCH 2/4] input: use kbd delays for send_key monitor command Gerd Hoffmann
2014-06-02 11:28 ` [Qemu-devel] [PATCH 3/4] input/curses: add kbd delay between keydown and keyup events Gerd Hoffmann
2014-06-02 11:28 ` [Qemu-devel] [PATCH 4/4] input/vnc: use kbd delays in press_key Gerd Hoffmann
2014-06-02 12:59 ` Dave Mielke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140602125930.GG10889@beta.private.mielke.cc \
--to=dave@mielke.cc \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).