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 626328 - 'use_action_appearance' property changes location when saving file
'use_action_appearance' property changes location when saving file
Status: RESOLVED DUPLICATE of bug 628253
Product: glade
Classification: Applications
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on: 628253
Blocks:
 
 
Reported: 2010-08-07 19:22 UTC by Severin Heiniger
Modified: 2010-12-31 04:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Demo UI file (681 bytes, application/x-designer)
2010-08-07 19:22 UTC, Severin Heiniger
Details

Description Severin Heiniger 2010-08-07 19:22:17 UTC
Created attachment 167338 [details]
Demo UI file

When saving a GtkBuilder UI file, 'use_action_appearance' properties (or 'related_action', respectively) reproducibly change their position in the list of properties of widgets related to a GtkAction. This is annoying because it clutters diffs and makes the actual changes harder to spot.

A file for the purpose of demonstration is attached. Take the following steps to reproduce it:

1. Open demo.ui in a text editor and notice that 'use_action_appearance' is located in the line above 'related_action'.
2. Open demo.ui using glade, select the widget 'test_button' by clicking on it, and save the file.
3. Open demo.ui in a text editor and notice that 'use_action_appearance' is located in the line *below* 'related_action'.
4. Open demo.ui using glade, select the widget 'test_button' by clicking on it, and save the file.
5. Go back to step 1.
Comment 1 Tristan Van Berkom 2010-08-29 15:57:18 UTC
Very interesting find.

I debugged this for a while and found it's actually a bug
in libgobject/gtk.

See bug 628253.
Comment 2 Tristan Van Berkom 2010-12-31 04:37:19 UTC
GObject bug has since been fixed, marking as a duplicate of fixed bug.

*** This bug has been marked as a duplicate of bug 628253 ***