From: Howard Spoelstra <hsp.cat7@gmail.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] regression in 2.8: unable to exit screen grab in SDL mode
Date: Fri, 16 Dec 2016 10:21:59 +0100 [thread overview]
Message-ID: <CABLmASHHFAWqSHFnc9uDGj6ZJKxP8495dCpKqLj4Kf2e=EOgrw@mail.gmail.com> (raw)
In-Reply-To: <20161216090024.GA4434@noname.redhat.com>
On Fri, Dec 16, 2016 at 10:00 AM, Kevin Wolf <kwolf@redhat.com> wrote:
> Am 16.12.2016 um 09:26 hat Thomas Huth geschrieben:
>> On 15.12.2016 20:19, Michael S. Tsirkin wrote:
>> > On Thu, Dec 15, 2016 at 09:15:27PM +0200, Michael S. Tsirkin wrote:
>> >> On Thu, Dec 15, 2016 at 05:25:50PM +0100, Gerd Hoffmann wrote:
>> >>>> Do we fix this or disable SDL altogether?
>> >>>
>> >>> Well, it can't be *that* bad, otherwise it would not went unnoticed for
>> >>> a whole release cycle.
>> >>
>> >> That's what I'm saying, maybe no one uses SDL anymore.
>>
>> It's maybe not as common as the GTK interface, but as far as I know
>> people still use the SDL interface. For example here:
>>
>> https://bugs.launchpad.net/qemu/+bug/922076
>>
>> ... so I would recommend to keep the SDL code in QEMU.
>
> When I actualy use qemu rather than just doing a quick test, I generally
> prefer SDL, too, because the GTK frontend still grabs some keys like F10
> for itself instead of passing them to the guest. And using HMP for
> something as simple as that - no, thanks.
>
> Kevin
>
I'd like to also point to the recent status report by Stefan Weil
concerning UI support in Windows builds:
http://lists.nongnu.org/archive/html/qemu-devel/2016-12/msg01383.html
At least for PPC Mac OS/OSX guests only the SDL1.2 UI is somewhat
usable, GTK2/3, SDL2 and VNC are all problematic.
Best,
Howard
next prev parent reply other threads:[~2016-12-16 9:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 14:25 [Qemu-devel] [PATCH for-2.8] ui/gtk: fix "Copy" menu item segfault Stefan Hajnoczi
2016-12-14 14:35 ` Stefan Weil
2016-12-14 15:15 ` Gerd Hoffmann
2016-12-14 22:49 ` Michael S. Tsirkin
2016-12-15 7:34 ` Stefan Hajnoczi
2016-12-15 7:48 ` Stefan Hajnoczi
2016-12-15 8:47 ` Kevin Wolf
2016-12-15 9:50 ` Stefan Hajnoczi
2016-12-15 4:35 ` [Qemu-devel] regression in 2.8: unable to exit screen grab in SDL mode Michael S. Tsirkin
2016-12-15 7:50 ` Stefan Hajnoczi
2016-12-15 9:17 ` Gerd Hoffmann
2016-12-15 14:55 ` Michael S. Tsirkin
2016-12-15 16:17 ` Gerd Hoffmann
2016-12-15 15:07 ` Michael S. Tsirkin
2016-12-15 16:25 ` Gerd Hoffmann
2016-12-15 19:15 ` Michael S. Tsirkin
2016-12-15 19:19 ` Michael S. Tsirkin
2016-12-16 8:26 ` Thomas Huth
2016-12-16 8:45 ` Liviu Ionescu
2016-12-16 9:00 ` Kevin Wolf
2016-12-16 9:21 ` Howard Spoelstra [this message]
2016-12-16 9:48 ` Gerd Hoffmann
2016-12-15 22:30 ` Michael S. Tsirkin
2016-12-16 9:27 ` Kevin Wolf
2016-12-16 9:36 ` 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='CABLmASHHFAWqSHFnc9uDGj6ZJKxP8495dCpKqLj4Kf2e=EOgrw@mail.gmail.com' \
--to=hsp.cat7@gmail.com \
--cc=crobinso@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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.