I have been all over the example code "ViewController", QCDocs,
nibs,
etc. and cannot figure out how QCView in this example automatically
connects
to the internal iSight camera (it works). Is this a default
behavior of
QCView or am I just missing something?
The magic lies in kCameraTitle (which is CustomCamera.nib)
The QCView in that nib is hardcoded to access the iSight. Open that
nib in IB. If you test it (Command-R), you'll see your iSight
output. if you click the QCView, and then click "unload" in the
Inspector Panel, it'll be blank the next time you test it.
According to the docs, they used iSight.qtz to see the input, but I'm
not entirely sure how that worked: attempts to open the qtz in QC
fail with a corruption error. Attempts to open in PropertyList Editor
say the same thing. Hexdumping it shows that it's at least partially
a binary plist(the headers look basically right), but it's been cooked
somehow. *shrugs*
Exploring the broken qtz may reveal how it works internally.
--
[ christopher wright ]
[EMAIL PROTECTED]
http://softpixel.com/~cwright/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
