Version 1.7.9.12 Changes

User Panels All Components

Exposed the box-sizing css style for all components which defines whether the border is a part of the overall component dimensions or outside of them. See https://www.w3schools.com/css/css3_box-sizing.asp for details regarding this style. Note that it may not have effect on the complex custom components.

User Panels Label Component

Exposed the text-align and line-height css styles for labels. See https://www.w3schools.com/cssref/pr_text_text-align.ASP and https://www.w3schools.com/cssref/pr_dim_line-height.asp for these properties.

The text-align property will allow you to align the text in the label component to the left, center, or right of the component. The line-height style may be used to center the content vertically.

HP202 ConsoleIp

This version adds an HP202 object with a read/write ConsoleIp property to the HP202 device. This property allows you to read and change which console an HP202 device is connected to. This feature still requires manufacturer testing and verification as we do not have any HP202 devices to test with.

Generic Emulator Tcp Client

This version adds a PingMessage and PingInterval property to Generic Emulators. These properties are primarily for use when the emulator is configured to use the TcpClient connection method. Leaving the PingMessage blank will mean this feature is not used.

When a remote device closes its tcp connection normally, there is a handshake that takes place that tells us the connection has been closed. The emulator will then try to start reestablishing the connection. However, if the remote device loses power or the connection dies in a way that does not allow the handshake to take place, then the DeviceEmulator will not know the connection is dead until either a failed operating system keepalive packet failure (which might take up to an hour or two) or until we attempt to send a message to the remote device. The ping property and ping interval allow you to define a message that gets sent every so often to make sure the connection is still working. These messages should be something that makes sense to the application on the remote end. It also allows us to test not only that the connection is still intact but that the application at the remote end is still responding. Note that it still may take longer than the interval time to detect a failure (often 15 to 60 seconds). Therefore, it does not make sense to set the interval too low.