> Is the part that I've put in bold true for all execution modes? Why is it > that this improves performance if when the patch doesn't contain OpenGL code? > Related to the last question (basically, the inverse), what happens if one > forgets to do this that would cause bad performance?
I haven't looked at the document fully (so I could be missing some context), but I don't think that statement's true generally. By itself, CGLMacro.h just defines a bunch of entry point expansions for gl functions. It also pulls in some other GL headers, but unless you're using actual GL functionality I don't think it would matter much. If you forget to include the file and you try to use GL you'll end up doing non-direct dispatched gl calls (you'll operate on the current context, which isn't necessarily the context QC wants you to use), so you'll probably just get bad results (or ok results if you're lucky - don't depend on being lucky though, just do the right thing). direct dispatch calls will save you a bit of time, but I'd be more concerned about correctness before performance. -- 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]
