Thanks Dan, Xav, Dennis and Eric,
The "Step Over" did not seem to obey me! ;-) It didn't seem to work and well I thought I misunderstood its use.
I ended up using the set multiple break points so I could hit "Run" and bypass that section but still have it run.
The one problem is that I am testing a mouseDown over a button and can't release the mouse to go ahead and hit the run button.
MouseDown with its limitations is kicking my butt right now. Big Time. I wish that at least one of the messages passed while in a mouseDown would not go back to the original control. If that was the case I would have been done three days ago.
Thanks again,
Tom
On Apr 27, 2005, at 12:23 PM, Dan Shafer wrote:
Tom.....
Can't you use "Step Over" instead of "Step Into" in those cases? Not tested, but it does seem like that's what ought to happen.
Alternatively, you could put in two breakpoints, one before and one after the loop. After the first breakpoint executes, hit "Run" in the debugger and things should stop at the next breakpoint, no?
On Apr 27, 2005, at 9:02 AM, Thomas McGrath III wrote:
Does anyone know how to bypass a lengthy repeat structure while in script debug mode? I still need the repeat to execute but I want to skip having to click through it.
I need to follow the script to find out where my problem is at but this repeat for each line x structure takes a couple hundred clicks to get through.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Shafer, Co-Chair RevConWest '05 June 17-18, 2005, Monterey, California http://www.altuit.com/webs/altuit/RevConWest
_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541
_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
