Ignition Features and Ideas

I have lost progress on projects and not been able to trace issues because Project Auditing was not enabled or configured correctly. I suggest a Gateway Setting to "Enable Default Project Auditing" and if enabled an Audit Profile selection. If set, any new project would be created already recording to the selected Audit Profile.

Add an easy way to add resources like icons or icon packs to the gateway.

instead focusing on developing module to create drawings in ignition, i strongly recommend to utilize Inkscape (add module or add on) so it can be used in Ignition.

When scripting, autocomplete is very useful to have. However, there are a few issues with it's functionality: Case sensitivity: typing system.util.getl does not autocomplete getLogger , since it is case sensitive If you make a typo or click somewhere, you must go all the way back to the previous . to re-open the autocomplete menu. Additionally, intellisense is very nice to have to know about function documentation. It is great for when you are offline and need to see function documentation. However, it too has issues: Also disappears when clicked away, and cannot be reopened without retyping Navigating with tab between arguments sometimes makes it disappear It does not reappear when you click back on the function or hover over it.

Builtin properties have pre-written documentation on them. Allowing custom properties and params to have similar documentation would be useful.

Add a project or page selection to run the script console code as though it was within the context of a page. For instance, in Perspective, this would allow properties, even session or custom properties, to resolve correctly during testing. It doesn't seem possible at first blush, but you guys have done the impossible before!

Are there any plans to add a dark theme to the ignition designer? I see that this question has been posted a few years ago but its 2020 now so I thought I would ask again.

For the builtin icons, it would be nice if icons had multiple descriptors that are searched against, rather than just the name (and instead of listing them twice). For example, "X" or "remove" might show the "close"/"clear" icons. As it is now, it can be faster to scroll through all icons than to guess different names an icon may be under (particularly a problem because material builtin doesn't contain all material icons). Sometimes, it is so hard to find that it becomes easier to just go to iconify and copy one in.

In scenarios where we may have multiple designers opened that are connected to unique gateways but happen to share the same project name and same gateway name yet differ by deployment mode (e.g. "dev" and "qa"), it would be nice to have the deployment mode also displayed at the top. Currently I have to dig down to the System tag provider in the tag browser to find the deployment mode tag to differentiate the two. The title could look something like: <Project Name> - <Gateway Name> | <Deployment Mode>

Symptom: Table object's selection is stuck after a refresh in the browser. Selected row and selected dataset holds the last value from before the refresh, and resetting these properties does not work. Setup: Table object, query binding that returned dataset with 3 columns. Row selection and multiple interval selection are enabled. Four columns are configured in column properties. The fourth uses a custom view to show a calculated status, with 'field' set to 'column_4', which does not exist in the dataset. The view has a parameters bound to the implicit 'value' and 'rowData'. Suspicion: Table object fails when 'value' is null/undefined for a column whose field isn’t in the dataset. This seems to leave the table’s selection state stuck after a refresh.