|
|
|
|
version 2003
PA_PackageInfo (packageNumber; pluginID; procPtr; data; resfile; name)
| Parameter | Type | Description | |
| packageNumber | short | → | Number of the plug-in |
| pluginID | short * | ← | ID of the plug-in packageNumber |
| procPtr | void ** | ← | Pointer to the code of plug-in packageNumber |
| data | void ** | ← | Private plug-in data |
| resfile | short * | ← | Resource file reference of the plugin packageNumber |
| name | char * | ← | Name (string) of the plug-in packageNumber |
Description
The routine
PA_PackageInfo
returns various information on the package whose internal range number is
pluginNumber
.
Pass the number of the plug-in in
packageNumber
. This number is in the range of 1 to the total number of opened plug-in.
You receive the ID of this plug-in in the short pointed to by
plugID
, the resource file reference number of this plug-in in
resfile
, a reference to its private data in
data
, and its name in
name
.
In
procPtr
, you receive a pointer to the code of the plug-in. This can be very useful in some cases since it lets you directly call some functions of another plug-in without using the
EXECUTE
routines (
PA_ExecuteMethod
,
PA_ExecuteFunction
, etc.).
Consult the FourDPack or Main function in 4DPluginAPI source code to see how you can call another plug-in. Be sure to send the
pluginData
as the plug-in will expect it and set the current resource file to plug-in resource file.
See Also
Error Handling
always returns
eER_NoErr