Thank you for the help Mark.
You said that is possible "create a variable in the editor, and reload the runtime. This way the changes are accepted without closing the runtime."
How i can do this? Could you tell me please
Thank You.
Thank you for the help Mark.
You said that is possible "create a variable in the editor, and reload the runtime. This way the changes are accepted without closing the runtime."
How i can do this? Could you tell me please
Thank You.
There are several ways of reloading.
All reload functionality is based on the principle, that there were changes in the editor, wich were compiled either by "create changed runtime files" or "create all runtime files"
internal reload from within the runtime: This internal reload is triggered from within the runtime, through the zenOn function "reload project online". This function can for example be called by the user through a button, or automated via a limit, rema, time-control etc. It is assumed that the runtime-files are already in the runtime directory (compiled in the editor on the same PC) or copied into the runtime directory (e.g. remote transport or manual copy) before executing this function.
external (remote) reload through remote-transport: When connecting to a PC with a runtime (either local or remote) by using remote transport in the editor, it is possible to reload the project remotely out of the editor, without the operator needing to interact. The changed runtime files can optionally be transferred with remote transport first as well.
external reload on clients: If there were changes on the server, and the server is reloaded, automatically, all clients will reload as well, getting automatically the changed runtime files from the server.
reload works with PCs running Windows, Terminals running XP Embedded or Windows CE and also on Webclients.