From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel <qemu-devel@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>
Cc: John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] Usability fixes for GTK2
Date: Sun, 26 Apr 2015 21:04:19 +0200 [thread overview]
Message-ID: <cover.1430075061.git.jan.kiszka@web.de> (raw)
Two small patches to fix annoying problems on GTK2. Both weren't tested
on GTK3 (no working setup at hand). The first one comes with a tiny risk
of behaving differently there. The second one may actually be required
on GTK3 as well or is at least a nop there and doesn't need the version
check.
Jan
CC: John Snow <jsnow@redhat.com>
Jan Kiszka (2):
gtk: Fix VTE focus grabbing
gtk: Avoid accel key leakage into guest on console switch
ui/gtk.c | 20 +++++++++++++++++---
1 file changed, 17 insertions(+), 3 deletions(-)
--
2.1.4
next reply other threads:[~2015-04-26 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 19:04 Jan Kiszka [this message]
2015-04-26 19:04 ` [Qemu-devel] [PATCH 1/2] gtk: Fix VTE focus grabbing Jan Kiszka
2015-04-27 9:23 ` Gerd Hoffmann
2015-04-27 12:26 ` Jan Kiszka
2015-04-26 19:04 ` [Qemu-devel] [PATCH 2/2] gtk: Avoid accel key leakage into guest on console switch Jan Kiszka
2015-04-27 9:24 ` 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=cover.1430075061.git.jan.kiszka@web.de \
--to=jan.kiszka@web.de \
--cc=jsnow@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.