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 623481 - unique_app_new should document startup_id as allow-none
unique_app_new should document startup_id as allow-none
Status: RESOLVED FIXED
Product: libunique
Classification: Other
Component: core
master
Other Linux
: Normal normal
: ---
Assigned To: libunique-maint
libunique-maint
Depends on:
Blocks:
 
 
Reported: 2010-07-03 17:06 UTC by Michael Terry
Modified: 2011-03-26 18:44 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Add (allow-none) annotation to parameter that can be NULL (1.68 KB, patch)
2011-02-16 23:11 UTC, Luciana Fujii 		committed Details | Review

Description Michael Terry 2010-07-03 17:06:24 UTC 
That way, the generated gir files will have startup_id be set as allow-none, so that NULL is allowed by bindings.
Comment 1 Michael Terry 2010-07-03 17:10:12 UTC 
Actually, that's true for a lot of parameters, like message_data in most places.  Search for "or %NULL" and you'll see them.
Comment 2 Luciana Fujii 2011-02-16 23:11:39 UTC 
Created attachment 181089 [details] [review]
Add (allow-none) annotation to parameter that can be NULL

The patch fixed unique_app_new and other methods to allow none parameters.
Comment 3 Emmanuele Bassi (:ebassi) 2011-03-26 18:44:52 UTC 
thanks, fixed in master