Load Jython Classes on Startup

[pturmel]

@Jonathan

It appears to me that the project library scripts do not load until a class is referenced in them.

Any named object, actually. And once-through is intended behavior, like import. Cross-thread dependencies are not supposed to impact this import mechanism (there's an import lock), but maybe IA has introduced a bug here.

Consider using a global lock object to ensure initialization doesn't happen in parallel (via system.util.getGlobals() or the similar system.util.persistent() from my LifeCycle module).

You may recall participating in this topic:

[IGN-5244]Persist Python Class Object

I am working in Perspective, but this probably applies to other modules as well. I have created user defined classes in the project scripts and I am instantiating them from a view in Perspective. Is there a place I can persist the instance of the object for use between events by the user? Right now I have it serializing to a property on the view, but when I want to work with the object again I have to de-serialize the object in order to work with it again. Having to write custom de-serialize me…

Edit: Bug found, work-around developed:

Project Library Script Initialization Races

Are you annoyed by pseudo-random breakage in Ignition project library scripting? Odd top-level constants being garbled, or operations in the top level that have side effects running twice? Or more? Not happening much, but always around project edits, and sometimes even on gateway restart? Yeah, me too. Poking around under the hood back in the spring, for a module development task, I ran across some problematic IA bytecode and pinged some people. But it went nowhere, as I co…