Listener Removal Strategy

Question

May be dumb - but I create a lot of objects in an application
written in 3.0. When they are done doing what they do, I would love
to be able to call a utility routine that shimply looped through
the listeners that are registered for all objects and remove them
where is .target is the object I am done with. I don't know if this
is possible but it would significantly simplify my code and I
suspect the internals of listener registration, removal and cycling
does the .target check anyways......
Am I barking up the wrong tree, is this something someone had
done or is the mere thought of it stupid from the start......
bob

Answer 1

Kglad - no, just the listeners. I would like something like
for each(listener in the listener stack) {
if listener.subscribed_to_target = mytarget
remove listener
In my coding - any listeners set up in an object are dealt
with by that object when done - typical remove_listeners funtion
removing listeners set-up, typically on instantiation of the
object. Listners that subscribe to the object events from other
objects deal with removal separately.
It would clean things up tremendously to simply walk the
listener stack and where the target is the object that is no longer
needed, I could have some iteration to remove all listeners that
have that object as a target.....
Hope this makes sense....
ccoonen - I fear the use of "weak reference" but do so as is
suggested in some texts. If I could confirm that the listener was
removed and collected as of a certain point I would follow your
strategy, but I always hesitate to rely on something I can not
test.