Vuo
1.2.5
|
VuoApp implementation.
Macros | |
#define | NS_RETURNS_INNER_POINTER |
Disable NS_RETURNS_INNER_POINTER (new in Mac OS 10.10's system headers), since Clang 3.2 doesn't support it. | |
Functions | |
bool | VuoApp_isMainThread (void) |
Is the current thread the main thread? | |
void | VuoApp_executeOnMainThread (void(^block)(void)) |
Executes the specified block on the main thread, then returns. | |
char * | VuoApp_getName (void) |
Returns the composition's name. | |
const char * | VuoApp_getVuoFrameworkPath (void) |
Returns the path of the folder containing Vuo.framework . | |
#define NS_RETURNS_INNER_POINTER |
Disable NS_RETURNS_INNER_POINTER (new in Mac OS 10.10's system headers), since Clang 3.2 doesn't support it.
void VuoApp_executeOnMainThread | ( | void(^)(void) | block | ) |
Executes the specified block on the main thread, then returns.
Can be called from any thread, including the main thread (avoids deadlock).
Don't call this from __attribute__((constructor))
functions, since this function depends on initialization which might not happen before your constructor is called.
char* VuoApp_getName | ( | void | ) |
Returns the composition's name.
If the composition is running in Vuo Editor (via VuoCompositionLoader), it extracts the name from the most-recently-loaded dylib's path. If the composition has been saved, this matches the composition's source filename. If not, it returns the text "Vuo Composition".
If the composition is running via VuoRunner (but not via VuoCompositionLoader), it returns the name of the VuoRunner process.
If the composition is running standalone, it tries the following Info.plist keys:
If none of those keys exist, it uses the composition executable's filename.
The caller is responsible for freeing the returned string.
const char* VuoApp_getVuoFrameworkPath | ( | void | ) |
Returns the path of the folder containing Vuo.framework
.
See also VuoFileUtilities::getVuoFrameworkPath.
bool VuoApp_isMainThread | ( | void | ) |
Is the current thread the main thread?