Hi All
I am on an interesting and long journey to master Ignition and just stumbled on something that surprised me.
On the Gateway there is a setting in Config\Gateway Scripting Project which is blank in my gateway. I heard from my colleague that it is always a good practice to set up Gateway Scripting Project - otherwise gateway scripts defined in the developer will execute in different and a lot less efficient way.
I hope it makes sense what i wrote. I don’t remember if this subject was mentioned in the ignition training and i wonder if anybody could please share some more info or confirm recommended approach.
So tag event scripts , gateway event scripts, message handlers (and I’m sure a few more that I’m not thinking about) aren’t scoped or part of a project. They are global gateway scope. So if you have a “common” library of scripting that you use across all your projects and the gateway scope objects need access to that, then you have to point this configuration to that project.
If you don't have a gateway scripting project set, then global scripting events (primarily, tag related, such as tag event scripts or runScript calls from tags) just won't work.
The 'gateway scripting project' has no relevance to 'gateway event scripts' you define in the designer (startup, shutdown, update, message handler, etc) - those are actually 'project' resources thus always 'know' which project they run under. Only truly global objects (tags) need a specific reference to use.
This should have been struck through as well. Or "global" inserted after "gateway". The gateway has multiple scopes: global, projects, and Perspective sessions (extended from a project scope). Vision clients have one scope, of the current project. The designer has two-ish: preview scope and script console scope, both of the current project, and not entirely separate.