qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] add input-send-event command
Date: Tue, 17 Jun 2014 05:54:35 -0600	[thread overview]
Message-ID: <53A02C7B.2010901@redhat.com> (raw)
In-Reply-To: <1402995735.1614.8.camel@nilsson.home.kraxel.org>

[-- Attachment #1: Type: text/plain, Size: 1616 bytes --]

On 06/17/2014 03:02 AM, Gerd Hoffmann wrote:
> On Mo, 2014-06-16 at 20:15 -0300, Marcelo Tosatti wrote:
>> Which allows specification of absolute/relative, 
>> up/down and console parameters.
> 
> Looks good overall, only minor nits.  Will wait for acks from qmp guys
> before picking into input branch.
> 
>> Suggested by Gerd Hoffman.
> 
> Huh?  Signed-off missing ...
> 
>> +Press left mouse button.
>> +
>> +-> { "execute": "input-send-event",
>> +    "arguments": { "console": 0,
>> +                   "events": [ { "type": "btn",
>> +                    "data" : { "down": true, "button": "Left" } },
>> +                    { "type": "btn",
>> +                      "data" : { "down": false, "button": "Left" } } ] } }
>> +<- { "return": {} }
> 
> Bad example.  Down + up should go as separate commands (so you have a
> sync inbetween), otherwise it might happen that the guest doesn't see
> the button event at all.

Would it be worth adding a command to the union of possible events that
adds a pause?  As in:

-> { "execute": "input-send-event",
    "arguments": { "console": 0,
                   "events": [
                    { "type": "btn",
                      "data" : { "down": true, "button": "Left" } },
                    { "type": "pause", "data": { "duration": 10 } },
                    { "type": "btn",
                      "data" : { "down": false, "button": "Left" } } ] } }

that sticks a 10 ms delay between the other two events?

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2014-06-17 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 23:15 [Qemu-devel] [PATCH] add input-send-event command Marcelo Tosatti
2014-06-17  9:02 ` Gerd Hoffmann
2014-06-17 11:54   ` Eric Blake [this message]
2014-06-17 13:41     ` Marcelo Tosatti
2014-06-17 11:59 ` Eric Blake
2014-06-17 13:46   ` Marcelo Tosatti

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=53A02C7B.2010901@redhat.com \
    --to=eblake@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mtosatti@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).