Bug 1161184

Hi Amos, I have got three question to make sure we'll do this correctly.

1) How do you number the consoles, i.e. how should I know what number should I use for the 'console' parameter?  And is it mandatory?  I presume we will always want to use '0' as that should represent the default (first) display, am I right?

2) What is the difference between:

{ "execute": "send-key", "arguments": { "keys": [{"type": "qcode", "data": "ctrl_r"} ] } }

and:

{ "execute": "input-send-event", "arguments": { "console": 0, "events": [ { "type": "key", "data" : { "down": true, "key": {"type": "qcode", "data": "ctrl_r" } } }, { "type": "key", "data" : { "down": false, "key": {"type": "qcode", "data": "ctrl_r" } } } ] } }

or do they have the same functionality?  I guess they do, I just want to be sure.

Thank you in advance for the answers.

(In reply to Martin Kletzander from comment #2)
> Hi Amos, I have got three question to make sure we'll do this correctly.
> 
> 1) How do you number the consoles, i.e. how should I know what number should
> I use for the 'console' parameter?  And is it mandatory?  I presume we will
> always want to use '0' as that should represent the default (first) display,
> am I right?

I posted a patch to make the 'console' parameter optional, so the default parameter should be none, then QEMU will use the first available console.
http://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg01188.html
 
> 2) What is the difference between:
> 
> { "execute": "send-key", "arguments": { "keys": [{"type": "qcode", "data":
> "ctrl_r"} ] } }
> 
> and:
> 
> { "execute": "input-send-event", "arguments": { "console": 0, "events": [ {
> "type": "key", "data" : { "down": true, "key": {"type": "qcode", "data":
> "ctrl_r" } } }, { "type": "key", "data" : { "down": false, "key": {"type":
> "qcode", "data": "ctrl_r" } } } ] } }
> 
> or do they have the same functionality?  I guess they do, I just want to be
> sure.

Yes. But we can split second command to two commands, even send other key events by input-send-event between two commands, it's more flexible.

> Thank you in advance for the answers.

Thank you.

The original need for input-send-event was fixed by other means, so this is just nice to have. Moving to upstream.

*** This bug has been marked as a duplicate of bug 636163 ***