All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Andrei Karas <akaras@inbox.ru>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] SDL2: only show consoles by shortcuts and not hide.
Date: Thu, 08 Sep 2016 08:10:09 +0200	[thread overview]
Message-ID: <1473315009.6698.10.camel@redhat.com> (raw)
In-Reply-To: <1473251067.637182699@f71.i.mail.ru>

On Mi, 2016-09-07 at 15:24 +0300, Andrei Karas wrote:
> >Среда,  7 сентября 2016, 14:27 +03:00 от Gerd Hoffmann <kraxel@redhat.com>:
> >
> >On Di, 2016-08-23 at 23:36 +0300, Andrei Karas wrote:
> >> This fix issue with stuck keys in SDL2 if press one of shortcuts
> >> for show/hide consoles.
> >
> >More detailed description please.  How exactly do you end up with stuck
> >keys?
> For example i using ctrl_grab=on option.
> Without patch if press rctrl+2 cosole window can be drawed and hidden at same time many times.
> Console drawed or hidden depend only how long keys was pressed.

Ah, so you hold down the hotkey and key autorepeat will show/hide the
window?

> >So, the hotkey works only in case the window is hidden, so you can't
> >hide windows with the shortcut any more.  Is that intentional?  Why?
> Because previous explanation i found only solution is limit this keys to
> always show windows.

You can check ev->key.repeat to detect whenever the keypress is a real
one or autorepeat event.

cheers,
  Gerd

  reply	other threads:[~2016-09-08  6:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23 20:36 [Qemu-devel] [PATCH 1/2] SDL2: only show consoles by shortcuts and not hide Andrei Karas
2016-09-07 11:27 ` Gerd Hoffmann
2016-09-07 12:24   ` Andrei Karas
2016-09-08  6:10     ` Gerd Hoffmann [this message]
2016-09-08 18:50       ` Andrei Karas
  -- strict thread matches above, loose matches on Subject: below --
2016-08-23 20:28 Andrei Karas

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=1473315009.6698.10.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=akaras@inbox.ru \
    --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.