|
|
|
Forum Newbie
Group: Forum Members
Last Login: 11/5/2008 1:38:50 PM
Posts: 9,
Visits: 20
|
|
Hi all,
I have a problem. I have three programs I'm trying to get to work. When I pilot them, I change the times to very small numbers so that I can see them run all the way through. And they work just fine. Then, when I set the times back to normal and my colleagues pilot them, they crash!! I have no clue why or how. They usually generate a "Device I/O Error". Any ideas?
-Kalif
|
|
|
|
|
Forum MVP
Group: Forum Members
Last Login: Today @ 3:46:25 PM
Posts: 336,
Visits: 894
|
|
Kalif,
Sorry, no answer for your problem, I just want to share a general thought on debugging. When I want to speed up a program for test runs, instead of changing all the times to very small numbers I just use Clock.Scale. E.g.,
Clock.Scale = 0.01
will speed everything up by a factor of 100. Just be sure to remove it before you run your experiment!
(Actually, I use a bit of script that gets triggered with a special Session Number and then lets me set the Clock.Scale, so I can leave the script in the final program and invoke it any time I need. But you get the idea.)
-- David McFarlane, Professional Faultfinder
|
|
|
|
