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 402941 - open/save without changes alters glade file
open/save without changes alters glade file
Status: RESOLVED DUPLICATE of bug 422823
Product: glade
Classification: Applications
Component: general
3.1.x
Other Linux
: Normal normal
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-31 19:11 UTC by Colin Watson
Modified: 2007-06-17 01:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
test case (157.44 KB, application/xml)
2007-01-31 19:12 UTC, Colin Watson
Details
diff between two states (51.63 KB, text/plain)
2007-01-31 19:13 UTC, Colin Watson
Details

Description Colin Watson 2007-01-31 19:11:28 UTC
If you repeatedly open and save the attached glade file, rather than staying the same, it will cycle between two states, each with a large chunk of changes between the states (diff also attached).

This is obviously extremely annoying when storing files in revision control. I don't mind (too much) if the output changes between versions of glade, as long as it's not too often, since I can just commit an otherwise no-op change with just those differences and ask all contributors to upgrade in sync, but it's a major problem for me when every change made in the UI will produce a significant diff.
Comment 1 Colin Watson 2007-01-31 19:12:22 UTC
Created attachment 81620 [details]
test case
Comment 2 Colin Watson 2007-01-31 19:13:25 UTC
Created attachment 81621 [details]
diff between two states
Comment 3 Colin Watson 2007-01-31 19:16:15 UTC
For anyone else encountering this, a workaround seems to be to hit Save twice in a row rather than once. I've informed my main contributor of this.
Comment 4 Vincent Geddes 2007-06-17 01:25:28 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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