From: Patrick Tseng <patricktsen@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/1] input-linux: provide hotkeys for evdev toggle
Date: Wed, 10 Jan 2018 09:06:03 -0800 [thread overview]
Message-ID: <CAG_FrSLEpZ8XugfbndEa2UO8yMGxetf2juS7ft-hUP2SRDF7qA@mail.gmail.com> (raw)
In-Reply-To: <20180110163003.GO3205@redhat.com>
Hi Daniel, thanks for responding.
> This should really be part of the commit message for the patch itself, so
it
> gets recorded in git history.
Next patch version I'll separate this out to another commit.
> I wonder if it is reasonable for ui/input-linux.c to honour the same
> global '-ungrab' configuration option ?
I had it as a global config option at first, but realized all config options
related to input-linux appears to be contained in it's own object-based
args, especially since evdev is still quite niche/isolated in its own way.
But I rather not make the decisions for input-linux, I'll leave that up to
the maintainer.
> If not, we should at least
> use the same syntax for describing the ungrab sequence. ie a list of
> key code names, rather than a hardcoded pair of numeric values.
This make sense, I agree it should at least be consistent.
- Patrick
(byxk)
On Wed, Jan 10, 2018 at 8:30 AM, Daniel P. Berrange <berrange@redhat.com>
wrote:
> On Sun, Jan 07, 2018 at 02:14:54PM -0800, byxk wrote:
> > Added some functionality to change the key combo for evdev toggle.
> > example:
> > -object input-linux,rhotkey=29,lhotkey=56,evdev=[etc...]
> >
> > Set the defaults to LCTRL and RCTRL if not provided.
>
> This should really be part of the commit message for the patch itself, so
> it
> gets recorded in git history.
>
> There is some overlap here with the grab sequence work John has just posted
> for cocoa frontend
>
> https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg05115.html
>
> I wonder if it is reasonable for ui/input-linux.c to honour the same
> global '-ungrab' configuration option ? If not, we should at least
> use the same syntax for describing the ungrab sequence. ie a list of
> key code names, rather than a hardcoded pair of numeric values.
>
>
> Regards,
> Daniel
> --
> |: https://berrange.com -o- https://www.flickr.com/photos/
> dberrange :|
> |: https://libvirt.org -o-
> https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o- https://www.instagram.com/
> dberrange :|
>
next prev parent reply other threads:[~2018-01-10 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 22:14 [Qemu-devel] [PATCH v2 0/1] input-linux: provide hotkeys for evdev toggle byxk
2018-01-07 22:14 ` [Qemu-devel] [PATCH 1/1] " byxk
2018-01-10 16:30 ` [Qemu-devel] [PATCH v2 0/1] " Daniel P. Berrange
2018-01-10 17:06 ` Patrick Tseng [this message]
2018-01-11 9:38 ` Gerd Hoffmann
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=CAG_FrSLEpZ8XugfbndEa2UO8yMGxetf2juS7ft-hUP2SRDF7qA@mail.gmail.com \
--to=patricktsen@gmail.com \
--cc=berrange@redhat.com \
--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).