...
GiD_SetColor : to specify a colour color for the mesh identified by the given id. The red, green, blue and alpha components should be between 0.0 and 1.0.
...
GiD_SetResultPointer : specifies the list with the result values for a given result's id. Following parameters may be set:
_t_gidBasicType basic_type : data type of the results, should be one of GIDPOST_FLOAT or GIDPOST_DOUBLE
_t_gidResultListType list_type : herewith the format of the results is specified. Should be one of GIDPOST_RESULTS: where all results are defined consecutively and will refer to the nodes / elements between 0 and num_results-1
GIDPOST_IDX_RESULTS: where each result is preceded by a label indicating its node /element number (should be a 4-byte integer)
_t_gidResultType result_type : type of result which will be defined. May be one of GIDPOST_SCALAR, GIDPOST_VECTOR_2 (vector result with 2 components), GIDPOST_VECTOR_3 (vector with 3 components), GIDPOST_VECTOR_4 (vector with 4 components, including signed modulus), GIDPOST_MATRIX_3 (matrix with 3 components Sxx, Syy and Sxy), GIDPOST_MATRIX_4 (Sxx, Syy, Sxy and Szz, GIDPOST_MATRIX_6 (Sxx, Syy, Sxy, Szz and Syz and Sxz), GIDPOST_EULER (with 3 euler angles), GIDPOST_COMPLEX_SCALAR (real and imaginary part), GIDPOST_COMPLEX_VECTOR_4 (2d complex vector: Vxr, Vxi, Vyr and Vyi), GIDPOST_COMPLEX_VECTOR_6 (3d complex vector: Vxr, Vxi, Vyr, Vyi, Vzr and Vzi) and GIDPOST_COMPLEX_VECTOR_9 (3d complex vector: Vxr, Vxi, Vyr, Vyi, Vzr, Vzi, |real part|, |imaginary part| and signed |vector|)
_t_gidResultLocation result_location : location of the result. May be one of GIDPOST_NODAL, GIDPOST_ELEMENTAL or GIDPOST_GAUSSIAN. At the moment GIDPOST_GAUSSIAN is not supported
int num_results : number of results in the list
unsigned int offset_next_element : distance in bytes between the beginning of result i and the beginning of result i+1. If 0 is entered then the reuslts results are all consecutive
const void *pointer : pointer to the list of results.
...
GiD_GetTclInterpreter : returns a pointer to GiD's global interpreter so that the plug-in can open their windows or execute their tcl Tcl scripts using the predefined tcl Tcl procedures of GiD.
The developer should keep in mind that all the plug-in code is executed inside GiD's memory space and so, all the memory allocated inside the plug-in should also be freed inside the plug-in to avoid memory accumulation when the dynamic library is called repeatedly. This also includes the arrays passed to GiD, which can be deleted just after passing them to GiD.