Zugg Software :: View topic - Feature suggestion. Improved loop detection. Reason included

Apprentice Joined: 01 Dec 2006 Posts: 178

Any chance for a loop detection that goes futher then detecting infinitive loops involving only one alias. Able perhaps detect loops as they happen where one alias triggers another? I just upgraded to 2.30 and when starting up my system the first time, something looped and locked but there's no way for me to find the loop since when I tried again to relog and such it didn't loop.

Posted: Sat Jul 05, 2008 3:16 am

The most common form of loop that I've noticed (aside from the obvious badly written alias) is when directly capturing data to a window, yet new windows are (or were, I assume still are) created with full permissions, so the original trigger capturing the data to the new window also fires on the data as it appears in the new window.

When this happens, it tends to disable the trigger, so it will not happen a second time around (though the script itself won't work either).

I don't know if this helps you track down that loop, but if you ever capture mapping data to a child window, that could be it.

Apprentice Joined: 01 Dec 2006 Posts: 178

The reason I ask for this is because of the it seem random loops , that shouldn't be there, but are for some reason happen.
As I described when I upgraded it looped for some reason, NO clue what and it outputted information that I don't have in my system to put out anywhere.
and since it was looping it was not possible stop it in any way. Or get more details.
Maybe an emergency break command or shortcut that overrides everything cmud is doing and forces parsing/triggers off.

And I've already exported cleared and reimported via xml so shouldn't be corruption anywhere.

ctrl + alt + shift + esc?

Posted: Sat Jul 05, 2008 3:19 pm

I had this once.. I think was a weird side effect of a button thing (gauge in my case) a while back. Some variable assignment on the buttons got switch around. I removed the variable references, saved it, and re-applied them.

Posted: Mon Jul 07, 2008 7:45 pm

It is very difficult to detect complex loops like this. The ESC key will abort anything running from the command line. For stuff running in the background, you can use the #THREAD command to look for the thread number and then use the #STOP command to stop the thread.