GNOME Bugzilla – Bug 615613
Use accessor functions instead direct access (use GSEAL GnomeGoal)
Last modified: 2010-06-14 17:37:07 UTC
See http://live.gnome.org/GnomeGoals/UseGseal for more details
Created attachment 158573 [details] [review] Use accessor functions Still remaining (no GTK+ api): GtkAccessible::widget GtkAssistant::forward GtkAssistant::back GtkObject::flags GtkTreeStore::stamp
Thanks for this! Please commit. The GtkAssistant fields are related to bug #596428. We don't need accessor functions so much as the enhancement described there implemented. Planning to take a shot at it myself when I find time, unless someone beats me to it.
Comment on attachment 158573 [details] [review] Use accessor functions commit 96421ff37cd554af1ac11527bcad25cc2f2f1930 Thank you for the review!
Hm. Can this bug be closed then? :)
Best leave it open for tracking purposes until we can actually build with GSEAL_ENABLE. This bug blocks bug #585391.
Status update: The GtkAccessible issue is fixed by using the new gtk_accessible_get_widget() function in GTK+ 2.21. The GtkAssistant issues are fixed by using the new gtk_assistant_commit() function in GTK+ 2.21. I just commented out with a FIXME message the one place in the "groupwise-features" plugin where it's referencing GtkTreeStore::stamp. GnomeCanvasItem adds its own flags to GtkObject::flags which we still have to check in plenty of places, so that's still an issue. GnomeCanvasItem could just as easily add its own flags member, but that would be an API + ABI break.
We now bundle libgnomecanvas in libart_lgpl in Evolution, and I gave GnomeCanvasItem its own flags field. So all issues are now solved. Closing as FIXED.