AppDelegate * DisplayLink Issues
Last week I focused on reworking a video matrix viewer from an old project structure (adopted from Apple’s LiveVideoMixer example), into a Cocoa Application (i.e. using an ApplicationDelegate). And, after quite a lot of cleaning up code, removing odd bits and digging into forums looking for tips on how to switch over (of which there are few)… I wasn’t able to get past this:
CVDisplayLinkStart(displayLink) == kCVReturnSuccess
Despite knowing that the displayLink object is not NULL… I simply couldn’t figure out what the problem was. So, I went back to the original structure and will rebuild the project in a different way from that foundation.
I learned along the way that linking objects using…
(id) anObject;
…allows you to connect outlets in Interface Builder without having to import the classes for the objects you wish to use.
We ran into this issue when using the Core Video framework and trying to import Box2D headers. There’s a clash that we couldn’t resolve. So, instead we can setup an independent object with a b2AABB world which will run the physics engine, and we can access it via a referenced outlet in the main video matrix view.
[ T ]
