I’m sorry to have frustrated you to this level. It is true that I jumped in at the deep end of Ignition, difficult enough in itself and made more difficult by my lack of experience in java programming.
Had I known it would be this difficult to write a module, I might have taken a different approach. But even after all this, I’m not sure that I would. We are evaluating Ignition. There are internal reasons why we need to use modules, and reasons why we need to know that modules will fill the need before spending a lot of time learning the top end of the system. True, we can do most of what we want with scripts, but that was not obvious when we started this evaluation. Once started down the module path, it made sense to keep on it, because we will need to come back to module development at some point.
I’m not allergic to Jython programming–I just left it to last. That’s where I am now, making the connection between the module and the project. I’m also new to Python, which is another reason I left it until the end. I had a lot going on with java and maven and the Ignition SDK.
I somehow missed the offline copy of the online Ignition manual. I thought I had read that there was no offline copy. I just looked through my folders and don’t see it. I’ll get a copy.
Bottom line is I hope you will bear with me, because you have helped–even when I didn’t fully adopt your suggested path for learning the system. I’m through the worst of it, not far from the end of the initial learning curve.
I’ll try to do a better job of searching the documentation before opening a new topic.