From: Nikola Pavlica <pavlica.nikola@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [PATCH] ui/gtk: Fix regression in gd_refresh_rate_milihz
Date: Sat, 08 Aug 2020 00:25:51 +0200 [thread overview]
Message-ID: <3ZSPEQ.MH51LARSPXFN2@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1451 bytes --]
From: Nikola Pavlica <pavlica.nikola@gmail.com
<mailto:pavlica.nikola@gmail.com>>
In January (I think), I suggested a fix for the constant refresh rate
issue in QEMU despite VMs being able to render graphics at a framerate
much higher than that.
Here's the link to the patch in question:
<https://lists.nongnu.org/archive/html/qemu-devel/2020-01/msg01343.html>
However, I've noticed that the fix for older systems that run a older
system of GTK fail to compile with my version of the patch. Which was
fixed here:
<https://lists.nongnu.org/archive/html/qemu-devel/2020-01/msg03386.html>,
but improperly.
The issue lies if the target system (that the package is build on) has
a higher version of GTK, let's say 3.24, it fails the #ifdef macro and
thus does not include the changes that I've made. I've noticed this
issue under the ArchLinux build system, which can be fixed by just
using the included macro for checking GTK versions.
Also being that this is a regression and not a plain bugfix, is this
mergable into stable?
Signed-off-by: Nikola Pavlica <pavlica.nikola@gmail.com
<mailto:pavlica.nikola@gmail.com>>
--- a/ui/gtk.c
+++ b/ui/gtk.c
@@ -1968,7 +1968,7 @@ static GtkWidget
*gd_create_menu_machine(GtkDisplayState *s)
*/
static int gd_refresh_rate_millihz(GtkWidget *window)
{
-#ifdef GDK_VERSION_3_22
+#if GTK_CHECK_VERSION(3, 22, 0)
GdkWindow *win = gtk_widget_get_window(window);
if (win) {
--
2.24.1
[-- Attachment #2: Type: text/html, Size: 2397 bytes --]
next reply other threads:[~2020-08-07 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 22:25 Nikola Pavlica [this message]
2020-08-08 1:00 ` [PATCH] ui/gtk: Fix regression in gd_refresh_rate_milihz Nikola Pavlica
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=3ZSPEQ.MH51LARSPXFN2@gmail.com \
--to=pavlica.nikola@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).