From: Paolo Bonzini <pbonzini@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Adding Save States menu items
Date: Thu, 6 Oct 2016 17:49:48 +0200 [thread overview]
Message-ID: <2f9fa744-bede-2d34-c991-3ba76e39a005@redhat.com> (raw)
In-Reply-To: <5F9A9486-71D8-4E80-99C9-924630F1B71B@gmail.com>
On 06/10/2016 17:48, Programmingkid wrote:
>
> On Oct 6, 2016, at 11:35 AM, Paolo Bonzini wrote:
>
>>
>>
>> On 06/10/2016 16:42, Programmingkid wrote:
>>>
>>> On Oct 6, 2016, at 10:28 AM, Peter Maydell wrote:
>>>
>>>> On 6 October 2016 at 15:22, Programmingkid <programmingkidx@gmail.com> wrote:
>>>>> Would you accept a patch that added "Save State" and
>>>>> "Restore State" menu items to the cocoa interface? They would
>>>>> allow the user to save the running state of the emulator.
>>>>
>>>> If you can get consensus on first adding those to one of the other
>>>> UI frontends that's better maintained than the cocoa UI,
>>>> then I would accept a cocoa UI patch that added them second.
>>>
>>>
>>> Ok, I will ask around.
>>>
>>> Does anyone else like the idea of having a "Save State" and
>>> "Restore State" menu items added to QEMU's gui?
>>
>> What would they do exactly?
>
> "Save State" would save the current running state of the emulator to
> file. "Restore State" would restore the saved running state. This
> feature is really good for cheating at video games and saving your
> work exactly as you left it.
Yes, but what would they do in QEMU terms? What would they call, when
would they be available, and how would the GUI behave?
Paolo
next prev parent reply other threads:[~2016-10-06 15:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 14:22 [Qemu-devel] Adding Save States menu items Programmingkid
2016-10-06 14:28 ` Peter Maydell
2016-10-06 14:42 ` Programmingkid
2016-10-06 15:35 ` Paolo Bonzini
2016-10-06 15:48 ` Programmingkid
2016-10-06 15:49 ` Paolo Bonzini [this message]
2016-10-06 16:04 ` Programmingkid
2016-10-06 16:17 ` Paolo Bonzini
2016-10-06 17:43 ` Programmingkid
2016-10-06 17:49 ` Peter Maydell
2016-10-06 17:51 ` Programmingkid
2016-10-06 20:03 ` Eric Blake
2016-10-06 19:59 ` Eric Blake
2016-10-06 20:10 ` Programmingkid
2016-10-06 20:26 ` Eric Blake
2016-10-07 7:21 ` Paolo Bonzini
2016-10-07 9:14 ` Daniel P. Berrange
2016-10-07 14:39 ` Programmingkid
2016-10-06 20:47 ` Peter Maydell
2016-10-06 21:07 ` Programmingkid
2016-10-07 8:46 ` Kevin Wolf
2016-10-07 9:09 ` Daniel P. Berrange
2016-10-07 14:55 ` Programmingkid
2016-10-07 14:57 ` Daniel P. Berrange
2016-10-07 14:59 ` Peter Maydell
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=2f9fa744-bede-2d34-c991-3ba76e39a005@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.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 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).