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 768819 - libgnomedbmm: HTML documentation uses GTK+ type when it really means a gtkmm one
libgnomedbmm: HTML documentation uses GTK+ type when it really means a gtkmm one
Status: RESOLVED OBSOLETE
Product: libgnomedbmm
Classification: Other
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: libgnomedbmm-maint
libgnomedbmm-maint
Depends on:
Blocks:
 
 
Reported: 2016-07-14 19:37 UTC by Daniel Boles
Modified: 2016-08-19 18:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Boles 2016-07-14 19:37:39 UTC
Just a tiny one for someone who's very bored someday. :-) Couldn't see a libgnomedbmm category so hope this is close enough, and it actually describes gtkmm anyway.

At the libgnomedbmm docs here:
http://www.gtkmm.org/docs/libgnomedbmm-3.0/docs/tutorial/html/ch03.html

We have an intro to the associated gtkmm, which lifts from its docs thusly:

> To obtain a gtkmm instance from a C GObject instance, use the Glib::wrap() function. For instance:
>
> GtkButton* cbutton = get_a_button();
> GtkButton* button = Glib::wrap(cbutton);

The last line, as in the tutorial this quote originated from -
https://developer.gnome.org/gtkmm-tutorial/stable/sec-basics-gobj-and-wrap.html.en - should read:

    Gtk::Button* button = Glib::wrap(cbutton);

HTH!
Comment 1 Kjell Ahlstedt 2016-08-05 14:26:30 UTC
I change the bug product to libgnomedbmm, as this is not a gtkmm bug.

As far as I know libgnomedbmm is an obsolete module that has not been maintained
for many years. I wouldn't be surprised if this bug will not be fixed.
Comment 2 Daniel Boles 2016-08-19 18:50:48 UTC
I thought it might be defunct but was worth double-checking. Yep, there's not much point in syncing/typo-correcting a doc mirror in an obsolete project. I'm happy to close in that case. Thanks for the reply!