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 629099 - GtkToolbar's is_important property isn't kept in mind when glade starts
GtkToolbar's is_important property isn't kept in mind when glade starts
Status: RESOLVED OBSOLETE
Product: glade
Classification: Applications
Component: user interface
git master
Other Linux
: Normal normal
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-08 18:50 UTC by Pablo Castellano (IRC: pablog)
Modified: 2018-03-26 15:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
main.ui (22.19 KB, application/x-designer)
2010-09-08 18:50 UTC, Pablo Castellano (IRC: pablog) 		Details

Description Pablo Castellano (IRC: pablog) 2010-09-08 18:50:52 UTC 
Created attachment 169794 [details]
main.ui

I have an ui design which contains a GtkToolbar with several GtkToolButtons and its associated GtkActions.

If I set/unset the is_important property through the glade interface it works fine showing/hiding the label of the action.
If I reopen the file, labels are not shown even if is_important is set.

Example attached.
Comment 1 Craig Keogh 2011-02-20 07:07:17 UTC 
When glade connects the GtkAction to GtkToolButton, the GtkAction properties are synced to the GtkToolButton (see gtk_tool_item_sync_action_properties [1]). 

Solution is to set 'is important' on the GtkAction.

Glade should help users avoid this situation, but I'm not sure how at the moment. Perhaps setting in the .glade GtkAction 'is important' on the users behalf, or maybe handling the situation on file load.

[1] http://git.gnome.org/browse/gtk+/tree/gtk/gtktoolitem.c#n621
Comment 2 GNOME Infrastructure Team 2018-03-26 15:15:29 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/glade/issues/69.