Specifications

COM+ reference
8
Glink: API reference manual Gallagher & Robertson
Constant definitions are slightly differently in the Glink for Java and Windows
versions due to differences in Java and COM+. In the Windows COM+ version,
the constants are global values rather than part of the actual class, so Java syntax
with a dot such as GlinkEvent.CONNECTED or GlinkKey.HOME become
GlinkEvent_CONNECTED and GlinkKey_HOME. This applies to all the
defined constants, e.g.:
GlinkEvent_STARTED
GlinkConfiguration_PROTOCOL_TNVIP
GlinkField_ATR_HIDDEN
GlinkApi_SEARCH_FORWARD
GlinkKey_TRANSMIT
The following methods are not supported or applicable to the Windows versions
ConfigServer
serverPort
userName
userPassword
traceMethod
The Glink for Windows version of the API also contains special 'constructor'
methods which allow you to create Glink objects that some GlinkApi methods
require as parameters. These are:
GlinkApi.GlinkPoint cursor position, X and y
GlinkApi.GlinkScreenArea used mainly for setting
GlinkEvent_SCREEN_AREA_MATCH
notifications
GlinkApi.GlinkConfiguration for creating new configuration objects
GlinkApi.GlinkKey for creating a utility key object
Programming techniques
Below are a few examples in programming the GlinkApi. Full examples were
installed in the "Samples" directory under the Glink installation directory.
Dual-interface, Type Library definition
The VTable definition is contained in GlinkApi's Type Library (TLB) included
in the GL.EXE file or the supplied GLINK.TLB resource file. Including the TLB