2 scripting questions

  1. is the list of system functions in the docs appendix a full list of all functions that are user accessible in the scripting engine?

  2. if i've got a program running on my machine, is there any better way to have it activate a script than the naive method of 'tie the script to a webdev route, have my program make an API call'?

this is unrelated to the other stuff i'm working on, i just thought of a naive hackish way to enable py3 scripting support in ignition without requiring any modifications to the current engine :slight_smile:

  1. There are deprecated functions that still work but are no longer in the documentation. Also, 3rd party modules can add more, like my Integration Toolkit.

  2. No. Use WebDev, or write a 3rd party module that installs a Servlet.

  3. Consider exposing an API in your external Python3 and letting Ignition call it with system.net.httpClient().

I was actually going to go the other way around, and write a py3 'ignition wrapper' that performed system function calls via webdev calls to specialized scripts that ran those functions in the scripting engine