All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Williamson <awilliam@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 5/5] keymap: consider modifier state when picking a mapping
Date: Wed, 19 Dec 2018 07:59:05 -0800	[thread overview]
Message-ID: <6c057e662b52f3dc23d580af5aa3de1a3e53e41e.camel@redhat.com> (raw)
In-Reply-To: <20181219111712.GI20465@redhat.com>

On Wed, 2018-12-19 at 11:17 +0000, Daniel P. Berrangé wrote:
> On Wed, Dec 19, 2018 at 10:42:14AM +0100, Gerd Hoffmann wrote:
> >   Hi,
> >  
> > > > This is quite horrible though. I'm more inclined
> > > > to revert this patch and find another way to fix the original problem
> > > > which won't require the UI frontends to track modifier state.
> > > 
> > > The UIs track modifier state anyway.
> > > 
> > > I fact I have some WIP patches to add a generic keyboard state tracker,
> > > so the UIs can use common code instead of having their own state
> > > tracking code each.  Also to make UI hotkeys configurable, consistent
> > > across all UIs we have.  Guess I should undust them, at least the state
> > > tracking part of it.
> > > 
> > > With that in place we can easily pass the full keyboard state to the
> > > keymap code.
> > 
> > Tried that:
> >   https://git.kraxel.org/cgit/qemu/log/?h=sirius/kbd-state
> 
> I've had a look & think that code makes sense & ought to be able to
> solve this problem.

I'll try and find a minute to do a scratch build with this patch (and
without my keymap patch) and throw it on openQA staging, since openQA
seems to do a great job of testing qemu input code. :P
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

      reply	other threads:[~2018-12-19 15:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-22  7:05 [Qemu-devel] [PATCH v3 0/5] keymap: support kbd layouts with multiple mappings for the same key Gerd Hoffmann
2018-02-22  7:05 ` [Qemu-devel] [PATCH v3 1/5] keymap: make struct kbd_layout_t private to ui/keymaps.c Gerd Hoffmann
2018-02-22  7:05 ` [Qemu-devel] [PATCH v3 2/5] keymap: use glib hash for kbd_layout_t Gerd Hoffmann
2018-02-22  9:11   ` Daniel P. Berrangé
2018-02-22  7:05 ` [Qemu-devel] [PATCH v3 3/5] keymap: numpad keysyms and keycodes are fixed Gerd Hoffmann
2018-02-22  7:05 ` [Qemu-devel] [PATCH v3 4/5] keymap: record multiple keysym -> keycode mappings Gerd Hoffmann
2018-02-22  7:05 ` [Qemu-devel] [PATCH v3 5/5] keymap: consider modifier state when picking a mapping Gerd Hoffmann
2018-12-18 18:45   ` Daniel P. Berrangé
2018-12-19  7:55     ` Gerd Hoffmann
2018-12-19  9:42       ` Gerd Hoffmann
2018-12-19 11:17         ` Daniel P. Berrangé
2018-12-19 15:59           ` Adam Williamson [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=6c057e662b52f3dc23d580af5aa3de1a3e53e41e.camel@redhat.com \
    --to=awilliam@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.