Events - TCP/IP COM

WDIPterm 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. OnTermData passes the data that was keyed or scanned into the terminal.

Terminal ID is always passed as 0-63. A terminal ID value of 99 is used as a placeholder for logging purposes.

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

You must set the ServerOn property to true before any events can be fired.

OnTermBaseRegister

Data passed:

basename, channel

Event:

A base station on client basename has successfully

 

powered up on channel and communicated with the

 

host computer via the serial connection.

OnTermSignIn6

 

Data passed:

basename, channel, terminal

Event:

A six-line terminal has signed in on channel at

 

client basename. Terminal ID is passed in terminal.

OnTermSignIn4

 

Data passed:

basename, channel, terminal

Event:

A four-line terminal has signed in on channel at

 

client basename. Terminal ID is passed in terminal.

OnTermSignOut

 

Data passed:

basename, channel, terminal

Event:

A terminal has signed out on channel at client

 

basename. Terminal ID is passed in terminal.

OnTermData

 

Data passed:

basename, channel, terminal, data

Event:

A terminal on channel at client basename has sent

 

data in response to an Input method call.

6-30

Page 85
Image 85
Worth Data 701 RF manual Events TCP/IP COM