sEndEvent (Function)

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

Closing the port
Using an external library: RXTX

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

sEndEvent (Function)

In french: sFinEvénement

Disables the detection of an event on a serial port. The event was managed by sEvent.

This function returns information regarding the server.

Versions 16 and later

This function is now available for Java applications.

New in version 16

This function is now available for Java applications.

Example

// Detect characters on COM1 port
sEvent(1, sEveCharReceived, "Read")
sEvent(1, sEveBreak, "Break")
...
sEndEvent(1, sEveBreak)
...

// --Procedure Read(PortNum, Event)
Trace(sRead(1, sInEntryQueue(1)))

Syntax

<Result> = sEndEvent(<Port number> [, <Event to stop>])

<Result>: Boolean

True if the function was run,
False otherwise.

<Port number>: Integer

Number of serial port (1, 2, 3, up to 32 for COM1, COM2, COM3, ... COM32).
Port number returned by sOpen (if this function was called with a port name).

<Event to stop>: Optional Integer constant (or combination of constants)

Event whose management must be stopped. If this parameter is not specified, all the events managed on the port are disabled.
sEveBreak Receive a "Break line" event
sEveCharReceived Receive a character
sEveCTS Change of CTS status
sEveDSR Change of DSR status
sEveTransmitCompleted The output buffer is empty
sEveError Detect an error on the line
Versions 16 and later
This constant is not available.
New in version 16
This constant is not available.
This constant is not available.
sEvePrinterError Printer error detected
Versions 16 and later
This constant is not available.
New in version 16
This constant is not available.
This constant is not available.
sEveEntryQueue80 The input buffer is full at 80%
Versions 16 and later
This constant is not available.
New in version 16
This constant is not available.
This constant is not available.
sEveRing Detect the "Ring" signal (ring)
sEveRLSD Change of RLSD status
Versions 16 and later
This constant is not available.
New in version 16
This constant is not available.
This constant is not available.

Remarks

Closing the port

When closing the port, all the events managed on this port are disabled. When re-opening the port, sEvent must be re-run to define the events managed on this port.

Versions 16 and later

Using an external library: RXTX

In Java, the use of functions for handling the serial and parallel ports (sOpen, sWrite, sRead, ...) requires the presence of an external library: RXTX.

This library includes a Jar archive and one or more native libraries that depend on the operating system on which the application is run. To use these functions:

the Jar archive (RXTXComm.jar) must:
- be found in the same directory as the Java application generated by WINDEV,
- be found in the execution classpath of the application,
- be directly included in the generated application (from the wizard for Java generation).
the native libraries corresponding to the operating system on which the application is run must be found:
- in the same directory as the Java application generated by WINDEV,
- in the path of the application libraries (librarypath).

The RXTX library and its documentation can be downloaded from: http://users.frii.com/jarvi/rxtx/index.html (link valid at the time this documentation was published).

Caution: The management of infrared ports is not available in Java.

New in version 16

Using an external library: RXTX

In Java, the use of functions for handling the serial and parallel ports (sOpen, sWrite, sRead, ...) requires the presence of an external library: RXTX.

This library includes a Jar archive and one or more native libraries that depend on the operating system on which the application is run. To use these functions:

the Jar archive (RXTXComm.jar) must:
- be found in the same directory as the Java application generated by WINDEV,
- be found in the execution classpath of the application,
- be directly included in the generated application (from the wizard for Java generation).
the native libraries corresponding to the operating system on which the application is run must be found:
- in the same directory as the Java application generated by WINDEV,
- in the path of the application libraries (librarypath).

The RXTX library and its documentation can be downloaded from: http://users.frii.com/jarvi/rxtx/index.html (link valid at the time this documentation was published).

Caution: The management of infrared ports is not available in Java.

Using an external library: RXTX

In Java, the use of functions for handling the serial and parallel ports (sOpen, sWrite, sRead, ...) requires the presence of an external library: RXTX.

This library includes a Jar archive and one or more native libraries that depend on the operating system on which the application is run. To use these functions:

the Jar archive (RXTXComm.jar) must:
- be found in the same directory as the Java application generated by WINDEV,
- be found in the execution classpath of the application,
- be directly included in the generated application (from the wizard for Java generation).
the native libraries corresponding to the operating system on which the application is run must be found:
- in the same directory as the Java application generated by WINDEV,
- in the path of the application libraries (librarypath).

The RXTX library and its documentation can be downloaded from: http://users.frii.com/jarvi/rxtx/index.html (link valid at the time this documentation was published).

Caution: The management of infrared ports is not available in Java.

Component : wd250com.dll