qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SDL2 UI behavior of switching views
Date: Tue, 30 Jan 2018 10:21:01 +0100	[thread overview]
Message-ID: <20180130092101.hiuru6lnzbjw2jiy@sirius.home.kraxel.org> (raw)
In-Reply-To: <alpine.BSF.2.21.1801291701130.88941@zero.eik.bme.hu>

On Mon, Jan 29, 2018 at 07:21:02PM +0100, BALATON Zoltan wrote:
> On Mon, 29 Jan 2018, Gerd Hoffmann wrote:
> > On Sun, Jan 28, 2018 at 06:43:44PM +0300, Anatoly Trosinenko wrote:
> > > When QEMU is run with GTK UI, it changes what is drawn on its single window
> > > when I press Ctrl-Alt-{1,2,3,4}. But when I use SDL2 UI, it opens multiple
> > > windows: a separate window per each view (display, monitor, serial,
> > > parallel). Is it by design or is it a bug?
> > 
> > It's intentional.  With gtk you can have separate windows too (try "View/Detach Tab").
> 
> Is there an option also to get back the old SDL1 behaviour with SDL2? Could
> that be made the default to make the transition easier?

Well, that kind of flexibility is alot harder to do with SDL as it
doesn't offer widgets to manage views ...

In contrast gtk has one widget per virtual console, and I can easily
shuffle around them: Just reparent from notebook to standalone window
("detach tab") and visa-versa (when closing the detached window).

How about using gtk instead?

cheers,
  Gerd

  reply	other threads:[~2018-01-30  9:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-28 15:43 [Qemu-devel] SDL2 UI behavior of switching views Anatoly Trosinenko
2018-01-29  8:27 ` Gerd Hoffmann
2018-01-29  9:45   ` Anatoly Trosinenko
2018-01-29 18:21   ` BALATON Zoltan
2018-01-30  9:21     ` Gerd Hoffmann [this message]
2018-01-30 13:35       ` BALATON Zoltan
2018-01-30 14:58         ` Gerd Hoffmann
2018-01-30 20:09           ` BALATON Zoltan
2018-01-31  7:13             ` 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=20180130092101.hiuru6lnzbjw2jiy@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=balaton@eik.bme.hu \
    --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).