Owner`s manual

Events – WD7802Term ActiveX

WD7802term events occur when a specific condition is met. When an event is "fired", an event handler

function in your application is called.

Though the details of exactly how it is done varies from one programming environment to the next, the

source code skeletons for the various event handlers are automatically generated and inserted into your

source code for you. See the samples for more specific information.

Each event passes relevant information to your event handler function. For example, OnTermData passes the

data that was keyed or scanned into the terminal.

Terminal ID is always passed as 0-999.

Once you have the event handler skeletons, you can proceed to add whatever functionality you desire to

each event.

Before any WD7802term events will fire, you must make sure to turn the Server on by calling

WD7802Term.InitializeServer

WD7802Term.ServerActive = True

OnServerActivate

Data passed: none

Event: Called when the ServerActive property is set to True immediately after the Server

begins listening for terminals.

OnTermSignIn

Data passed: terminal

Event: A terminal has signed in. Terminal ID is passed in terminal.

OnTermSignOut

Data passed: terminal

Event: A terminal has signed out. Terminal ID is passed in terminal.

OnTermData

Data passed: terminal, data

Event: A terminal has sent data in response to an Input or SendBatchProgram method call.

OnTermNotSignedIn

Data passed: terminal

Event: A command has been sent to a terminal that is not signed in.

OnTermSequenceError

Data passed: terminal

Event: The one-for-one host prompt/terminal response protocol has been violated. The host

cannot send a second Input command until it has received a response from the first

Input command. If WD7802Term receives 5 sequence errors in a row, a Host Logic