It may happen that the DIALOGKBD screen does not open from the login screen in the runtime.

• Related Articles

• It may happen that a zenon Runtime deadlock occurs in combination with the "DIALOGKBD" screen.

  Summary When using for example a color palette change function on a "DIALOGKBD" screen, a dialogue will be open and at least the zenon Runtime gets into a deadlock. Also affects SAP RFC function calls where the dialog shows up. Description When using ...

• It should be possible to open the DIALOGKBD screen relatively to the position of the login screen in the runtime.

  Summary Unlike the SETVALUEKBD and the SETSTRINGKBD, the DIALOGKBD screen does not use relative positioning to the calling screen or element, but the coordinates of the frame linked, so that in specific circumstances the element to which is being ...

• The start/end functions of the DIALOGKBD screen may be executed unintentionally in the Runtime.

  Summary The start/end functions of the DIALOGKBD screen are executed during every screen switch, independently the DIALOGKBD is visualized or not in the Runtime. DescriptionThe start/end functions of the DIALOGKBD screen are executed during every ...

• The User name control element of the Login screen may not be updated in the Runtime.

  Summary Although the login is successful, the User name control element of the Login screen may remain empty after a user enters the login name using the Keyboard screen in the Runtime. DescriptionAlthough the login is successful, the User name ...

• The automatic keyboard may not open in a specific screen type in the runtime.

  Summary The automatic keyboard may not open in the active directory user administration screen when clicking on the domain, username or password control elements in the runtime. DescriptionThe automatic keyboard may not open in the active directory ...