diff options
author | Matthias Clasen <mclasen@redhat.com> | 2017-12-26 14:04:33 -0500 |
---|---|---|
committer | Matthias Clasen <mclasen@redhat.com> | 2017-12-26 14:39:49 -0500 |
commit | 5ec25cde21ede68bf423a50386d35265a049b777 (patch) | |
tree | f130f2bdb0b7a50efa0e515aadaa60670b769905 /gdk/gdkcursor.c | |
parent | 6374226d6b2f49f88a3e526c03f9b0f968043dd8 (diff) | |
download | gtk+-5ec25cde21ede68bf423a50386d35265a049b777.tar.gz |
cursor docs: Point to gtk_widget_set_cursor
This is the right API to use for applications.
Diffstat (limited to 'gdk/gdkcursor.c')
-rw-r--r-- | gdk/gdkcursor.c | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/gdk/gdkcursor.c b/gdk/gdkcursor.c index d5e03d7c65..57a80fc837 100644 --- a/gdk/gdkcursor.c +++ b/gdk/gdkcursor.c @@ -48,7 +48,9 @@ * * Cursors by themselves are not very interesting, they must be * bound to a window for users to see them. This is done with - * gdk_window_set_cursor(). + * gdk_window_set_cursor() or gdk_window_set_device_cursor(). + * Applications will typically use higher-level GTK+ functions such + * as gtk_widget_set_cursor() instead. * * Cursors are not bound to a given #GdkDisplay, so they can be shared. * However, the appearance of cursors may vary when used on different @@ -57,7 +59,7 @@ * There are multiple ways to create cursors. The platform's own cursors * can be created with gdk_cursor_new_from_name(). That function lists * the commonly available names that are shared with the CSS specification. - * Other names may be available, depending on the platform in use. + * Other names may be available, depending on the platform in use. * Another option to create a cursor is to use gdk_cursor_new_from_texture() * and provide an image to use for the cursor. Depending on the #GdkDisplay * in use, the type of supported images may be limited. See |