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 322819 - GtkRadioButton lacks value/current-value API
GtkRadioButton lacks value/current-value API
Status: RESOLVED DUPLICATE of bug 166995
Product: gtk+
Classification: Platform
Component: Widget: Other
2.8.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-11-30 09:55 UTC by Jorn Baayen
Modified: 2010-10-26 06:38 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Proposed patch (9.40 KB, patch)
2005-11-30 09:56 UTC, Jorn Baayen 		none Details | Review

Description Jorn Baayen 2005-11-30 09:55:36 UTC 
GtkRadioButton lacks value/current-value API that GtkRadioAction exposes.
Comment 1 Jorn Baayen 2005-11-30 09:56:29 UTC 
Created attachment 55410 [details] [review]
Proposed patch

If this is considered the right approach, I can provide a patch against
GtkRadioMenuItem as well.
Comment 2 Björn Lindqvist 2008-04-02 22:27:59 UTC 
What is the purpose of the patch? Could you maybe provide an example on how to use this new api and how it makes things better so to speak?
Comment 3 Jorn Baayen 2008-04-03 07:28:54 UTC 
This would make binding the value of the RadioButton to a GConf property easier, especially using libgconf-bridge.
Comment 4 Emmanuele Bassi (:ebassi) 2008-04-03 07:36:45 UTC 
this bug should really be a dupe of bug 166995 (which has a patch as well, but it has been reviewed).
Comment 5 Björn Lindqvist 2008-04-04 15:34:00 UTC 
Then hm... Let's close it as a dupen then?


*** This bug has been marked as a duplicate of 166995 ***
Comment 6 Yaron Sheffer 2010-10-26 06:38:50 UTC 
This was never fixed, and neither was its duplicate. Now the same functionality is needed for g_settings_bind.

(In reply to comment #5)
> Then hm... Let's close it as a dupen then?
> 
> 
> *** This bug has been marked as a duplicate of 166995 ***