Echelon LNS Plug-in - Manual (Page 48)

Name Type Description
Prelaunch Long The optional Prelaunch property allows a director
to launch the plug-in in the background, typically
when the director is started. Not all directors
support the use of pre-launch, and if not this
property is ignored, and the plug-in would never be
pre-launched by that director. When the plug-in is
pre-launched, the plug in should remain running in
the background until a command to that plug-in is
sent from the director, at which point the plug-in
should become visible and behave normally. This
allows plug-ins with a long launch time to be called
quickly once the director is running.
A plug-in implementing the Prelaunch property
must also define the Prelaunch value in the
Windows registry. The Windows registry key is
described in Implementing the Plug-in Object Class
in Chapter 2.
If you are using the LNS Plug-in Framework, you
can also use the Prelaunch field of the PluginInfo
static property of the plugin’s object class to have
the registry value set for you.
A plug-in supporting pre-launch operation should
not display any messages or become visible while
going through the pre-launch sequence. A director
can tell a plug-in to pre-launch by setting the
Prelaunch property to 1.
RemoteFlag Boolean Optionally set by the director to indicate if the
plug-in is running on the same computer as the LNS
Object Server (RemoteFlag is False) or on a
different computer (RemoteFlag is True). In the
remote case, the director will set this property before
setting the NetworkName property. If RemoteFlag
is True, the RemoteTransport property should also
be set.
RemoteTransport Read-write
Long
The enumeration specifies the remote client type. It
should only be set if the RemoteFlag property is
True.
For LNS full clients, set this property to 1.
For LNS lightweight clients, set this property to 2.
Top Long The y location, in pixels, of the upper left corner of
the plug-in’s main window. 0 is at the topmost of
the user’s display.