All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] gtk: Fix accelerator filtering
Date: Mon, 25 Mar 2013 07:51:57 -0500	[thread overview]
Message-ID: <877gkvod5e.fsf@codemonkey.ws> (raw)
In-Reply-To: <514F40A2.6000202@web.de>

Jan Kiszka <jan.kiszka@web.de> writes:

> On 2013-02-25 16:44, Jan Kiszka wrote:
>> On 2013-02-25 16:39, Anthony Liguori wrote:
>>> Jan Kiszka <jan.kiszka@siemens.com> writes:
>>>
>>>> This is in fact very simply: When the input in grabbed, everything
>>>> should be exclusively passed to the guest - except it has our magic
>>>> CTRL-ALT modifier set. Then let GTK filter out those accels that are in
>>>> use. When checking the modifier state, we just need to filter out NUM
>>>> and CAPS lock.
>>>
>>> Can you explain what you're fixing?
>> 
>> That it's not filtering what it is supposed to.
>> 
>>>
>>> We shouldn't hard code modifiers like this.  The reason you give
>>> accelerators paths like this is so that they can be overridden by a
>>> user.
>>>
>>> That's why I filtered by path.  Once we're running, we shouldn't assume
>>> that accelerators use the modifiers we started with.
>> 
>> Your path-based filtering does not work as it uses an unsupported
>> internal function (see my other mail).
>> 
>> We can make the modifier configurable via QEMU means (command line
>> parameter, gconfig, whatever). But let's get the basics working first.
>
> The bug still exists, my patch still applies. Unless you have some idea
> for a better solution, please apply this for now so that CTRL-q inside a
> guest doesn't kill more kittens.

Hi Jan,

Your patch breaks overriding accelerators which as I said before is a
critical accessibility feature.

The current code works for me but I realize it's using an unsupported
interface.  I'll spend some time today trying to find a work around.
But we definitely cannot assume that the accelerators are using any
specific modifiers.

Regards,

Anthony Liguori

>
> Jan

  reply	other threads:[~2013-03-25 12:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1361367806-4599-1-git-send-email-aliguori@us.ibm.com>
     [not found] ` <1361367806-4599-10-git-send-email-aliguori@us.ibm.com>
     [not found]   ` <5127B788.40701@siemens.com>
     [not found]     ` <5127BBC1.5070607@siemens.com>
     [not found]       ` <512B7B8B.1000402@siemens.com>
     [not found]         ` <87zjys9zcv.fsf@codemonkey.ws>
     [not found]           ` <512B86E7.80603@siemens.com>
2013-03-24 18:06             ` [Qemu-devel] [PATCH v2] gtk: Fix accelerator filtering Jan Kiszka
2013-03-25 12:51               ` Anthony Liguori [this message]
2013-05-07 21:03               ` Jordan Justen
2013-05-07 22:42                 ` Jan Kiszka
2013-07-17  6:54                   ` Jan Kiszka
2013-07-17 13:02                     ` Anthony Liguori
2013-07-22  7:04                       ` [Qemu-devel] [PATCH v3] " Jan Kiszka

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=877gkvod5e.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=jan.kiszka@web.de \
    --cc=kwolf@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.