https://bugzilla.gnome.org/show_bug.cgi?id=696428
gtk+ | general | unspecified
Domenico Ferrari <domfe> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |do...@tiscali.it
--- Comment #4 from Domenico Ferrari <do...@tiscali.it> 2013-09-05 08:36:26 UTC
---
I'm using win32. How can I debug my application if it always issues a warning?
>From the reference manual
"--g-fatal-warnings. Make GTK+ abort on all warnings. This is useful to stop
on the first warning in a debugger, if your application is printing multiple
warnings. It's almost always best to start debugging with the first warning
that occurs."
Also the message is incorrect. The backend IS supported, it cannot set the
cursor theme and maybe the user want the default... I haven't changed the
cursor theme or size.
The function settings_update_cursor_theme is called from
gtk_settings_get_for_screen when creating the default settings.
If you can't handle it in the backends I think you should call, in
settings_update_cursor_theme, the functions
gdk_*_display_set_cursor_theme for every backends actually supported in
gdkdisplaymanagers.c:gdk_backends and eventually do nothing in the backend if
it cannot do that and ignore silently the request.
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
Wayland-bugs mailing list
Wayland-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
