|
From: | Akihiko Odaki |
Subject: | Re: [PATCH v3] ui/cocoa: Take refresh rate into account |
Date: | Tue, 21 Jun 2022 18:04:47 +0900 |
User-agent: | Mozilla/5.0 (X11; Linux aarch64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 |
On 2022/06/21 17:51, Peter Maydell wrote:
On Mon, 20 Jun 2022 at 21:29, Akihiko Odaki <akihiko.odaki@gmail.com> wrote:Retreieve the refresh rate of the display and reflect it with dpy_set_ui_info() and update_displaychangelistener(), allowing the guest and DisplayChangeListener to consume the information.But why? What goes wrong if we don't bother to do this? thanks -- PMM
Regarding dpy_set_ui_info(), it depends on the guest. update_displaychangelistener() would change the frequency of the calls of the DisplayChangeListener.
I think it is obvious that delivering the refresh rate with dpy_set_ui_info() and update_displaychangelistener() makes sense, considering that those functions actually exist. They shouldn't exist at first place if we don't have to bother to do this.
Regards, Akihiko Odaki
[Prev in Thread] | Current Thread | [Next in Thread] |