Re: Memory Leak - NSView with custom accessibility info
Re: Memory Leak - NSView with custom accessibility info
- Subject: Re: Memory Leak - NSView with custom accessibility info
- From: Mike Engber <email@hidden>
- Date: Fri, 28 Apr 2006 09:08:59 -0700
So, NSNibAXRelationshipConnector, implies you're setting some of your
accessibility attributes up using Interface Builder.
Try not setting any of them in Interface Builder. Instead, do it by
calling accessibilitySetOverrideValue: in your code (e.g. in
awakeFromNib). Setting up attributes in Interface Builder is not
magic - it's simply a convenient way to get
accessibilitySetOverrideValue: called for you at nib loading time.
If that fixes the leak, then you'll a) have a workaround and b) be
able to file a bug against Interface Builder
(NSNibAXRelationshipConnector).
-ME
I can see (using ObjectAlloc) all of the retains and releases that
have been performed on our NSView object, so I can see where the
accessibility code is retaining me and not doing any releases. I can
match all of the other retains and releases to each other but there
seem to be 4 extra retains in the NSNibAXRelationshipConnector when
the bundle is being loaded.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden