| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
It's an opaque type, which means you can't actually do anything with it (which is why there is no API reference to it) all you can do is pass it in to QuartzComposer methods that take image types. The proper type would be "id" (note there is no *, id is a pointer type already)
There's no reason to do this. I'm not really sure what it would do, but since you later overwrite the sourceImage with the output of your renderer it's almost certainly leaking something. Technically, you would not even need the sourceImage variable as Objective-C allows you to do this: [v001DestinationRenderer setValue:[v001SourceRenderer valueForOutputKey:@"SourceOutput1" ofType:@"QCImage"] forInputKey:@"DestinationInput1"]; On Feb 8, 2008, at 10:58 AM, vade wrote:
|
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden This email sent to email@hidden
| References: | |
| >Fastest way to pass images from one QCComposition to another - QCPortImage? CVPixelBuffer? (From: vade <email@hidden>) | |
| >Re: Fastest way to pass images from one QCComposition to another - QCPortImage? CVPixelBuffer? (From: Troy Koelling <email@hidden>) | |
| >Re: Fastest way to pass images from one QCComposition to another - QCPortImage? CVPixelBuffer? (From: vade <email@hidden>) | |
| >Re: Fastest way to pass images from one QCComposition to another - QCPortImage? CVPixelBuffer? (From: vade <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.