From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v4] ui/cocoa: Use NSWindow's ability to resize
Date: Mon, 28 Feb 2022 09:32:19 +0900 [thread overview]
Message-ID: <a8877602-f3d6-11e7-b2e9-068c76bf8d94@gmail.com> (raw)
In-Reply-To: <CAFEAcA_OprFX4ub6dYzTNmwP7y2D31AmhknQ0xjQ11jYw8Nxig@mail.gmail.com>
On 2022/02/27 23:56, Peter Maydell wrote:
> On Sat, 26 Feb 2022 at 10:41, Akihiko Odaki <akihiko.odaki@gmail.com> wrote:
>>
>> This change brings two new features:
>> - The window will be resizable if "Zoom To Fit" is eanbled
>> - The window can be made full screen by clicking full screen button
>> provided by the platform. (The left-top green button.)
>>
>> Signed-off-by: Akihiko Odaki <akihiko.odaki@gmail.com>
>> ---
>> ui/cocoa.m | 543 +++++++++++++++++++++++++----------------------------
>> 1 file changed, 252 insertions(+), 291 deletions(-)
>
> This is making too many changes in a single patch to be
> reviewable -- can you break it down into more digestible
> chunks, please?
>
> thanks
> -- PMM
Unfortunately it is not possible. The most of the change is caused by
the convergence of two windows (full screen window and normal window)
into one. ui/cocoa depends on them for coordinate calculations and event
handling, which happens basically everywhere in QemuCocoaView. The old
implementation with two distinct windows and the new one with a unified
window are essentially incompatible and cannot be mixed.
Regards,
Akihiko Odaki
prev parent reply other threads:[~2022-02-28 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 10:40 [PATCH v4] ui/cocoa: Use NSWindow's ability to resize Akihiko Odaki
2022-02-27 14:56 ` Peter Maydell
2022-02-28 0:32 ` Akihiko Odaki [this message]
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=a8877602-f3d6-11e7-b2e9-068c76bf8d94@gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--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).