|
|
||||
UPDD supports an application program interface (API) on all supported platforms. This allows user written programs to interact directly with the driver or pointer device handled by UPDD. It is assumed that the reader is familiar with the various functions and parameters of TBUPDD, since that information is not duplicated here.
The API calls work exactly the same in all environments except obvious operating system specific calls.
Registry get and set setting calls work exactly the same in all environments.
In Windows they access the registry whereas in other operating systems they
access the files holding the registry structure.
Depending on which operating system and client language is used the user has a choice of linking to the API statically or dynamically. For example on Windows both static and dynamic libraries are available, however Visual Basic only supports dynamic linking.
Depending on the OS in use the following files implement the UPDD API:
|
|
|
|
TBapi.h TBbundle.h Tbapi.lib Tbapi.dll Tbapi.bas * Tbbundle.bas *
|
function declarations. contains bundle-specific data (file supplied with driver). statically linked implementation. dynamically linked implementation. contains DLL function declarations, constants and data types and helper functions for VB. contains VB bundle specific data.
* both these files are required in a VB project
|
|
|
|
|
TBapi.h TBbundle.h TBApi.lib |
function declarations. contains bundle-specific data (file supplied with driver). statically linked implementation for a given target processor
|
|
|
|
|
TBapi.h nonwindows.h nonwininternals.h TBbundle.h libTBApi.a |
function declarations. declarations of Windows specific constructs for non Windows targets declarations of Windows specific constructs for non Windows targets contains bundle-specific data (file supplied with driver). statically linked implementation.
|
|
|
|
|
TBapi.h nonwindows.h nonwininternals.h TBbundle.h libTBApi.so
|
function declarations. declarations of Windows specific constructs for non Windows targets declarations of Windows specific constructs for non Windows targets contains bundle-specific data (file supplied with driver). dynamically linked implementation.
|
|
|
Java applications will need to use the Java Native Interface (JNI). This can link using either the DLL or the static library. A partial JNI interface is available, but not yet supported - this is supplied in source form to simplify JNI implementation. |
Full details of the version 4 SDK and API are currently being documented in the advanced technical SDK dialog. For further information please visit the SDK and API page on our web site.
Contact
For further information or technical assistance please email the technical support team at technical@touch-base.com.