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 708188 - Fix default properties introspection once for all
Fix default properties introspection once for all
Status: RESOLVED OBSOLETE
Product: glade
Classification: Applications
Component: general
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-09-16 19:43 UTC by Juan Pablo Ugarte
Modified: 2018-03-26 15:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Juan Pablo Ugarte 2013-09-16 19:43:29 UTC
Glade uses default values defined in the parameter spec of the property to determine if a property should be saved or not in the xml file.

But sometimes the runtime has a different value because either its a bug or a derived class changed it its init function.

This was the source of several annoying bugs over time.
So lets see if we can fix this issue for real.

For this I propose a new approach to properties defaults introspection

Patch 
https://bug625867.bugzilla-attachments.gnome.org/attachment.cgi?id=254955

Ok so this patch take a completely new and radical approach to determine the
proper default value of a property.

We simply ignore defaults declared in the parameter specs and create a dummy
instance of each object class we keep in GladeAdaptor and update the defaults
from that instance while cloning parent properties (see
gwa_clone_parent_properties())

This seems to work just fine, and it could even let us deprecate save-always
flag in the catalog and avoid all kind of stupid bugs like this one!

Of course these kind of changes belong to the early start of a development
series and not a few days before making a stable release.

so for glade-3-16 I think i will go with the workaround proposed in my previous
comment!

cheers!
Comment 1 GNOME Infrastructure Team 2018-03-26 15:31:34 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/138.