After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 91922 - No way to get default Gdk::Cursor
No way to get default Gdk::Cursor
Status: RESOLVED NOTABUG
Product: gtkmm
Classification: Bindings
Component: general
2.0
Other other
: Normal normal
: ---
Assigned To: gtkmm-forge
gtkmm-forge
Depends on:
Blocks:
 
 
Reported: 2002-08-28 22:31 UTC by ÉRDI Gergõ
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ÉRDI Gergõ 2002-08-28 22:31:35 UTC 
Some methods (like gdk_window_set_cursor and gnome_canvas_item_grab) use 0
for their GdkCursor* argument to indicate a (re)setting of the default
cursor. There's no way to get this cursor with Gdkmm.

One possibility would be a static get_default() method in Gdk::Cursor that
returned some special Gdk::Cursor that returns 0 in gobj()
Comment 1 Murray Cumming 2002-08-29 08:16:49 UTC 
It's really the "parent's cursor" rather than the "default cursor".
I'm not sure that I want a
Gtk::Cursor(bool
use_the_parents_cursors_whenever_this_gtkmmcursor_is_used)
constructor.

Both Gdk::Window::set_cursor() and Gnome::Canvas::Item::grab() already
have overloads that allow the use of the parent's cursor instead of
specifying one.
Comment 2 Murray Cumming 2002-09-04 13:34:25 UTC 
So, should I close this as NOTABUG?
Comment 3 ÉRDI Gergõ 2002-09-04 15:12:13 UTC 
Yes