Ignition v8.1.35
Curious to know of any pitfalls with my project.
This alludes from one of my last questions about class instances.
I have a working project and the way I did it is as follows.
There are many sessions each with the same custom properties defined, with each property value being set by a session’s respective memory tags on session start.
I have an “admin dashboard” where a user can change the value of an online session’s custom property value from a table.
Instead of messaging the target session of the change, I write the change to a saved reference of the target session. On session startup, it will log itself to a dictionary defined globally in project script. When a user needs to change a value in a session, it just changes the value stored in the dictionary for the respective key.
I created a class that takes the session as an argument and use property getters/setters for modifying the session.custom values.
While this does work, it doesn’t “feel” correct.
That is, relying on the value change propagating to the source object by reference only. It seems a message handler should handle/marshall change requests to the required session. Thoughts?