Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Debugger
Message
From
06/03/2006 21:40:25
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
 
 
To
05/03/2006 16:15:44
Mike Smith
Doncaster Office Services
Oakville, Ontario, Canada
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Environment versions
Visual FoxPro:
VFP 8 SP1
Miscellaneous
Thread ID:
01101549
Message ID:
01101912
Views:
13
>Charles:
>
>This is reply number #2 to your helpful message about the debugger.
>
>I used the SET STEP ON feature and was able to get the debugger to come up in a good way so thank you for this.
>
>But what I found was really weird. When I have the debugger activate then RUN TO CURSOR, my code performs correctly. When I take out the SET STEP ON line, the code performs incorrectly.
>
>The issue was that the buttons on the previous form were not disabling. With SET STEP ON, I can watch the code go through the disable method and then RUN TO CURSOR shows the buttons disabling properly.
>
>So my code seems OK, but when I take out SET STEP ON, the method for disabling is ignored.

I haven't read the whole thread, just want to jump in with a few possible things that may happen while debugging:

- you switch between debugger (in its own frame, not _screen) and your app. Your form's .activate may fire before returning to the place in code where you have suspended execution. Your grid(s) may refresh.

- anything timing critical may work in the debugger (because you're so damn slow with your mouse, takes you millions of nanoseconds between clicks) while it may not without it. This is a hint that you may consider looking for a good place to plant a DoEvents(), or it is not, it depends :)

- with an active timer ticking, your debugging experience may get you to new heights of... well, anything, on steroids. Depending on your setting in menu-options-tools-debug, you may or may not see timer events in the debugger. Also, if the timer doesn't disable itself while executing its code, you may see second timer event starting before you've stepped out of the first. Set the interval to less than a second to feel the steroids :).

So, while debugger is the alleged neutral observer, it really isn't. It's just a good tool if you want to track what's going on inside your code, and it's quite good on the job. It, however, isn't perfect, and... well, when you develop your hammer usage skills, sooner or later you come upon the thing about the thumb, right? Same here.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform