Screen Switch in Web Engine takes very long when multiple scripts/functions are used

• Related Articles

• FAQ: When I start my zenon project on a Service Engine client, my AUTOSTART script is not executed. What is the problem?

  A "script" in zenon is not a snippet of code as you may think in the traditional sense, but rather a configured collection of zenon functions, executed in order. A common use of a zenon script is to load several screens at project startup, for ...

• Button as switch shows invalid state before a variable value is available

  Summary A button element configured as a switch displays an invalid state in the Service Engine before a variable value is available. This behavior has been modified. Description When a screen is opened in the Service Engine, a button element that is ...

• FAQ: Which IE version is used by the HTML screen? Which Plugins can be executed?

  The HTML-screen created in zenon does not use the default-browser installed on the operating system. It uses the pre-installed rendering-engine of Microsoft, called "Microsoft Web Browser Control". This program emulates the Internet Explorer. ...

• When using the HTML Web Engine, loading the screens in a browser takes a very long time.

  Summary Larger projects can take a very long time to load screens in the HTML Web Engine. This may cause the runtime to be unusable, if several screen switches cause the Web Engine to permanently load for several minutes. DescriptionLarger projects ...

• HTML5-Element based 3D element can be used in Windows / Web Visualization Service / Web Engine

  Summary A new web-based 3D integration is now available. This can be integrated via ActiveX screen elements. Description Only the *.glb format is supported. Functionalities can be triggered in the 3D Integration via limit violations. A prerequisite ...