> The following does not work, it returns an invalid image whose textureName is > 0, and reported width and height is 0, and cannot be passed to another > QCRenderers published input image port.
I don't know if this worked on older builds, but I don't see how it can work reliably as advertised -- there's no guarantee that the texture is generated on the same CGL context (or in the same sharegroup), so the name could be meaningless. In practice I don't think this happens, except when QC is managing the CGL context itself -- if you supply the context, it will pretty much use that one and others it creates in the same sharegroup, so it would work, but only based on luck. Getting a name without knowing what sharegroup it's valid on is useless. If you provided 2 non-shared CGL contexts to 2 QCRenderers, the texture couldn't possibly be used by both (IOSurface is the correct way to address this issue; unfortunately QC doesn't really handle that feature). I'd be interested to know if this worked in earlier builds. -- Christopher Wright [email protected] _______________________________________________ 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]
