AUGraph Documentation
AUGraph Documentation
- Subject: AUGraph Documentation
- From: Andrew James <email@hidden>
- Date: Tue, 9 Nov 2010 23:25:07 -0800 (PST)
I wanted to ask a question about the docs in regards to the AUGraph error kAUGraphErr_CannotDoInCurrentContext.
I have XCode 3.2.4 installed and here is documentation for this error:
To avoid spinning or waiting in the render thread (a bad idea!), many of the calls to AUGraph can return: kAUGraphErr_CannotDoInCurrentContext
. This result is only generated when you call an AUGraph API from its render callback. It means that
the lock that it required was held at that time, by another thread. If you see this result code, you can generally attempt the action again - typically the NEXT render cycle (so in the mean time the lock can be cleared), or you can delegate that call to another thread in your app. You should not spin or put-to-sleep the render thread.
My concern is that I have a misunderstanding or the above is not entirely accurate. I have a graph with nodes that have not been connected. The graph itself has not been opened either.
During unit tests I am delibarately trying to generate errors to make sure that they will be appropriately handled. In this case, I call AUGraphStart( ... ) on the graph as described above. I am NOT calling it from the render callback. This seems to be different than the "is only generated" clause from above.
It appears that the
error under question can also be used to indicate operations that are not supported by the current state of the graph. Am I missing something or could the docs be modified slightly to represent true intent of this error?
Cheers,
--aj
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden