Hi there,
I am trying to make a basic table that will display some of the device status. I have already made UDT's using bit masking to get all the values I want.
Additionally, i have been able to make a template and tie it to a the UDT and make the UDT instances drag and drop. This has worked well.
The trouble is I'm looking at this for about 125+ processors and was thinking a table might be the way to go. I tried doing this a prospective table and can get data bound and working, but only entry by entry. Nothing to make creating it 125 times simple.
I am fairly new with ignition so my approach could be completely wrong. I'm looking for feedback on if I'm even headed the right direction. and if so, maybe some pointers on where I can study up. I have poked around through the manual, watched a ton of videos on Inductive University and Youtube. All help is welcomed.
Perspective or Vision?
This will change the methods you get quite a bit.
I am open to both. We have mix of vison and perspective.
If this is Vision, change your template to accept a tag path string parameter, and use an indirect binding inside the template.
Then use a template repeater with a dataset of your 125 tag paths to create all the instances you want.
You can do basically the exact same thing in Perspective, using a "template" view and the flex repeater.
Just to check, the reason to use tag paths is due to much better performance from indirect tag bindings, compared to UDTs, yes?
Getting this to work using perspective's built in table would be possible (if you have a binding for each element in the table), but you'd want to generate these bindings with scripting, which is beyond my level of knowledge.
The footgun in Vision is specifically the UDT parameters you can add as custom properties. Because of the way they work, if you bind to a UDT parameter you're reading all of the UDT, all the time, even if you only need a couple of individual tags within it for whatever your template/etc is doing. If you use indirect tag bindings, you're forced to be more deliberate about which elements you actually pull out.
