16.04.2018, 19:25
(16.04.2018, 15:32)Daniel. Wrote:Thanks Daniel(16.04.2018, 13:55)ncgnick Wrote: Thank you all
All that was the obvious reaction from my side.
It would be easier if there was a straight forward procedure. This would keep the project more readable
Just think of a project with 5000 GAs and a central function switching off everything. I wouldn't even think of such a solution and I wouldn't dare to let all the feedbacks pass through all the line couplers and routers just for the visualization
Developers, please consider this functionality in future firmware releases
In that case you need other way around.
Tag all your local status objects.
Create event based script on your central group and paste this code
Change 'YourTag' to your tag.Code:value = event.getvalue()
myobjects = grp.tag('YourTag')
myobjects:update(value)
BR
I must admit that this is more efficient than my solution which was close to that but I built the object list manually.
I like efficient code. This solution contributes also the documentation because one can find the general function members easily