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 572904 - GtkRadioAction broken in trunk
GtkRadioAction broken in trunk
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Class: UIManager / Actions
2.15.x
Other Linux
: Normal major
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 572896
 
 
Reported: 2009-02-23 20:40 UTC by Mathias Hasselmann (IRC: tbf)
Modified: 2009-02-26 09:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mathias Hasselmann (IRC: tbf) 2009-02-23 20:40:13 UTC 
In trunk it is possible to deactivate GtkToggleActions by pressing them again.
This behavior is unexpected and a regression towards previous versions of GTK+.

See bug 572896.

Could it be that GtkAction and their proxies don't properly synchronize their properties anymore?

See also bug 570172.
Comment 1 Matthias Clasen 2009-02-23 21:32:51 UTC 
You mean GtkRadioActions, but yeah, looks like a gtk bug.
Comment 2 Mathias Hasselmann (IRC: tbf) 2009-02-23 21:35:00 UTC 
Indeed, GtkRadioAction.
Comment 3 Murray Cumming 2009-02-23 23:05:12 UTC 
Dave/Michael (CCed), it would be an educational exercise to find out what svn commit introduced this problem.
Comment 4 Tristan Van Berkom 2009-02-26 02:40:15 UTC 
This is fixed with my last commit to trunk, (at least tests/testactions
displays the correct behavior now).

Note the problem seemed to be specific to toggle type proxies
used with radio actions.
Comment 5 Mathias Hasselmann (IRC: tbf) 2009-02-26 09:49:20 UTC 
(In reply to comment #4)
> This is fixed with my last commit to trunk, (at least tests/testactions
> displays the correct behavior now).
> 
> Note the problem seemed to be specific to toggle type proxies
> used with radio actions.
> 

Will look at your patch later as I am not convinced that the bug is specific to toggle type proxies: As already noticed in bug 570172, property synchronization seems to work fundamently different now. Well, but I really didn't have the time to look at the details yet.