VCOM:VectorWorks:Scripting:IPythonWrapper::Call: Difference between revisions

From Vectorworks Developer
Jump to navigation Jump to search
m (1 revision)
No edit summary
Line 15: Line 15:
<def>
<def>
<funcDef lang="cpp">
<funcDef lang="cpp">
virtual boolVCOM_CALLTYPE Call(const char* functionName, const TXStringArray& arrParams) = 0;
virtual bool VCOM_CALLTYPE Call(const char* functionName, const TXStringArray& arrParams) = 0;
</funcDef>
<funcDef lang="cpp">
virtual bool VCOM_CALLTYPE Call(const char* moduleName, const char* functionName, const TXStringArray& arrParams) = 0;
</funcDef>
</funcDef>
</def>
</def>

Revision as of 13:49, 19 September 2013

Description

namespace VectorWorks::Scripting

Member of VCOM:VectorWorks:Scripting:IPythonWrapper

...put some description here...

virtual bool VCOM_CALLTYPE Call(
const char* functionName,
const TXStringArray& arrParams) = 0;
virtual bool VCOM_CALLTYPE Call(
const char* moduleName,
const char* functionName,
const TXStringArray& arrParams) = 0;

Parameters

functionName const char* no info.
arrParams const TXStringArray& no info.

Return Value

Uses standard VCOM Error Reporting.

Return value meaning:

kVCOMError_NotInitialized Bad VCOM instance used to call the fuction.
kVCOMError_Failed Routine failed.

Version

Availability: from Vectorworks 2014