Config Bridge: call unbind_all automatically when object is destroyed

Bug #459681 reported by Michal Hruby on 2009-10-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Desktop Agnostic Library for GLib-based Projects
Low
Michal Hruby

Bug Description

It's a pain to override dispose/finalize handler for each object that uses ConfigClient.bind method, just to call unbind_all in those (not to mention problems when you bind to a property of a standard object and problems this makes for bindings - people don't tend to think about cleaning up in python). LDA already has all necessary info to do the cleanup itself (lists of all bindings per object), therefore I'd be really helpful if the unbind_all was called automatically when the object is destroyed.

Related branches

Mark Lee (malept) on 2009-10-27
Changed in libdesktop-agnostic:
importance: Undecided → Low
summary: - Call unbind_all automatically when object is destroyed
+ Config Bridge: call unbind_all automatically when object is destroyed
tags: added: config feature-request
Mark Lee (malept) on 2010-04-18
Changed in libdesktop-agnostic:
assignee: nobody → Michal Hruby (mhr3)
milestone: none → 0.3.90
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers