FROM : Jason Horn
DATE : Thu Nov 29 23:59:03 2007
I have a simple app that has a controller 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.
DATE : Thu Nov 29 23:59:03 2007
I have a simple app that has a controller 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.
| Related mails | Author | Date |
|---|---|---|
| Jason Horn | Nov 29, 23:59 | |
| Jonathan Hess | Nov 30, 09:37 | |
| Jason Horn | Nov 30, 14:15 |






Cocoa mail archive

