From 173c19eb5a09f2706becda72a321ad1082f987c6 Mon Sep 17 00:00:00 2001
From: Alessandro Astone <ales.astone@gmail.com>
Date: Wed, 21 Aug 2024 12:33:36 +0200
Subject: [PATCH] fix: Avoid ambiguous overload when calling
 Gdk::Cursor::create (#7070)

Since gtkmm 4.15.0 a new overload for Gdk::Cursor::create exists
which creates an ambiguity when passing a string literal.

We can avoid the ambiguity by explicitly constructing a Glib::ustring
from the string literal before calling the method.

https://gitlab.gnome.org/GNOME/gtkmm/-/issues/159
---
 gtk/MainWindow.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gtk/MainWindow.cc b/gtk/MainWindow.cc
index 5ac237249..0c592f286 100644
--- a/gtk/MainWindow.cc
+++ b/gtk/MainWindow.cc
@@ -887,7 +887,7 @@ void MainWindow::set_busy(bool isBusy)
     if (get_realized())
     {
 #if GTKMM_CHECK_VERSION(4, 0, 0)
-        auto const cursor = isBusy ? Gdk::Cursor::create("wait") : Glib::RefPtr<Gdk::Cursor>();
+        auto const cursor = isBusy ? Gdk::Cursor::create(Glib::ustring("wait")) : Glib::RefPtr<Gdk::Cursor>();
         set_cursor(cursor);
 #else
         auto const display = get_display();