Posted: January 29 2003 at 19:43 | IP Logged

Found something interesting tonight.   If the returned value is zero to the jump command the program hangs.

Running XP on P3-450

Keith

Posted: January 30 2003 at 11:43 | IP Logged

Keith,

The program doesn't actually "hang"...it just goes into an infinite loop because it will jump continuously to the same line .

I could change this so that if a result of 0 was returned, the program would either just exit the macro or possibly go to the next line, but this would interfere with people who have a formula in the jump command where they might be intentionally looping back to the same line waiting for criteria in the formula to change causing a jump value other than 0 to be returned.

Dave.

Posted: February 01 2003 at 14:52 | IP Logged

But is'nt that the same as the wait command?

I'd at least like to see a dialog box that comes up while it is in the endless loop to let you cancel.

Thanks for considering.

Keith

Posted: February 03 2003 at 10:49 | IP Logged

Keith,

The wait command is actually different.  When PowerHome is looping due to a "Jump" command, all other events are suspended and will wait until the current macro containing the jump command completes.

A "Wait" command will halt execution of the macro, store all of its variables, start a timer for the specified number of seconds, and then exit.  Processing of events will continue and the program will not be "hung".  When the timer expires, the macro will be reloaded into the execution queue and processing will continue at the line following the "Wait" with the macro variables restored.

I would rather not have a dialog box appear because then PowerHome would be truly "hung" while waiting for the user to respond. 

Would you be happy with an option that changes any jumps of 0 to a 1 or perhaps limits the number loops?

Dave.

Posted: February 04 2003 at 20:33 | IP Logged

Dave,

I'm concerned with the "programus-oop-us" situation.  

Either a changeable default of 0 to 1 would work or a loop limit would be fine.

Just put the termination or change from 0 to 1 in the event log for debugging.

How about a spell checker on the forum??

KC

Posted: February 07 2003 at 11:19 | IP Logged

I'll include some options in the Setup so that the user can select to disable the endless looping and log the situation.  Monitoring for a keypress would just slow down the macro processing and I want to keep that as lean as possible.

Dave.