Re: View object not accessible from controller object
Re: View object not accessible from controller object
- Subject: Re: View object not accessible from controller object
- From: Jonathan Hess <email@hidden>
- Date: Fri, 30 Nov 2007 00:37:18 -0800
Hey Jason -
At runtime, is the instance variable set to nil, or is it set to some
random address that doesn't point to a VideoView object? And what
exactly are you doing that causes the crash? Does something like
videoView->iVar crash? or [viewView message].
If it's [videoView message], then you've probably over released, or
under retained your videoView and are messaging it after it's been
dealloced. If it's videoView->iVar, then that would crash with either
a nil, or garbage value.
Hope that gives you the clue you need -
Jon Hess
On Nov 29, 2007, at 2:59 PM, Jason Horn wrote:
ontroller and a custom view object called VideoView. My app was
working fine until I started doing some interface improvements, and
now I get exec_bad_access whenever the controller tries to send a
message to the VideoView object. I have figured out that, even
though the VideoView object is initialized correctly when the nib
file loads, and even though I connected VideoView to the controller
with an a controller outlet, it's as if the object isn't there. In
debugging, I can see that there is no object pointed to by the
outlet (again, even though I connected it in IB).
Does anyone know what would would cause this behavior? I have tried
everything I can think of, including deleting and recreating the
VideoView object, and re-connecting to the controller in IB.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden