Visibility of button with image file in HTML5 WebEngine sometimes does not work

Visibility of button with image file in HTML5 WebEngine sometimes does not work

Summary

Due to a congestion of variable updates during a screen switch elements could not be updated sometimes.

This is now fixed by properly queueing variable updates when a screen switch occurs.

Description

Due to a congestion of variable updates during a screen switch elements could not be updated sometimes.

This is now fixed by properly queueing variable updates when a screen switch occurs.

Information

-



Issue Number: 187361
Fixed on Date: 9.7.2019
Versions: 8.00 0 BUILD 59775

    • Related Articles

    • Checklist: HTML Web Engine

      Time estimate: 20 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Screenshot and followed ...

    • visibility dooesn't work for HTML mdi element browserwindow

      Description In the Service Engine, visibility and flashing do not work as expected for the "Browser window" screen element of the HTML screen. These functionalities cannot be reliably controlled dynamically. This behavior has been modified. Dynamic ...

    • Checklist: Smart Client does not work

      Time estimate: 20 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

    • Flashing synchronization does not work in the HTML Webengine

      Summary There were two issues regarding WebEngine and flashing/blinking. There was an issue with the flashing state of elements in the WebEngine. It is expected that the flashing state of all flashing elements is the same at a given time. E.g. the ...

    • WebEngine Docker Image loads cert bundle from wrong location

      Description The HTML Web Engine cannot establish a connection under Linux. The cause is that the certificate bundle is loaded from the wrong location in the Docker image. Even if the environment variable is configured correctly in the container, ...