Script not always triggered after property change
I made a vb script which takes about 5 to 10 seconds to execute. If i trigger it directly from a verb button, the pg2 display will freeze for 5 to 10 seconds which is bad because then there will be no feedback of the progress of the script. Therefore i made it trigger by a property change in the Control Module aspect which works good. But after navigating around in the workplace the script will eventually not be triggered. If i run the script manually it works again for some time but after a few minutes of navigating through the workplace it doesn't get triggered.
My question:
Is there a better way to run a script and keep the pg2 responding or how can I fix the fact that my script eventually can't be triggered anymore?
My question:
Is there a better way to run a script and keep the pg2 responding or how can I fix the fact that my script eventually can't be triggered anymore?
Asked 1 year ago
Answers
0
Better use eg a calculation to do the job in the background instead of bonding the realtime sensitive HMI to a synchronous action.
by dionbartelen Rank: 1234 on 6/7/2019 5:16:04 AM | Like (0) | Report
My question is moved to vb graphics but to clarify:
These are pg2 graphics witch toggle a boolean in control builder, if that boolean changes, a script aspect will run. This is the script that does not always run.
Add new comment