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 562182 - gtk_init() docs inaccurate
gtk_init() docs inaccurate
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Documentation
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-11-24 21:55 UTC by Behdad Esfahbod
Modified: 2011-01-04 16:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Behdad Esfahbod 2008-11-24 21:55:23 UTC
The docs currently say:

"Note that there are some alternative ways to initialize GTK+: if you are calling gtk_parse_args(), gtk_init_check(), gtk_init_with_args() or g_option_context_parse() with the option group returned by gtk_get_option_group(), you don't have to call gtk_init()."

The part "you don't have to..." is only partially true.  If I want to parse arguments, then fork, then open display I have to use either gtk_parse_args() or gtk_get_option_group(FALSE), then fork, then call gtk_init().

The docs for gtk_parse_args() also say: "You shouldn't call this function explicitely if you are using gtk_init(), or gtk_init_check()."  The "shouldn't" part is wrong.  It should be "You don't need".