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 702811 - Widget with related action, setting visibile or sensitive still produces effect
Widget with related action, setting visibile or sensitive still produces effect
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Class: UIManager / Actions
3.9.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-06-21 12:41 UTC by Domenico Ferrari
Modified: 2018-05-02 15:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Domenico Ferrari 2013-06-21 12:41:47 UTC 
If a widget (GtkButton) has a related action set and the action is hidden and not sensitive, the code below changes the behavior of the button.

  g_object_set(G_OBJECT(button), "visible", TRUE, NULL);
  g_object_set(G_OBJECT(button), "sensitive", TRUE, NULL);

I'm expecting that visible and sensitive are valid only when changed through the related action.
Comment 1 Daniel Boles 2017-06-05 17:31:25 UTC 
I'm not sure this is really a problem.

If you set an Action on a widget implementing GtkActionable, its visibility and sensitivity should become exclusively controlled by that Action, and other code should not try to override these properties. IMO, it is fine to leave such cases as a programmer error, rather than making the toolkit spend time preventing it.

Do you have a rationale of how a situation would arise where these properties would be subject to change, and that change must be blocked, and how it's not a programmer error to get into that situation?
Comment 2 GNOME Infrastructure Team 2018-05-02 15:41:03 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/428.