At 15:50 2015-12-12, Richard Kaye <[email protected]> wrote:
The one I specifically mentioned to Kurt, ASSERT .f., will. I used
this quite extensively just recently where I was working on a form
that, for better or worse, has a lot of optional configurations and
I'm moving or hiding controls. Sometimes I wanted to let the code
run after making some changes and other times I wanted to step
through. Using ASSERT .f. instead of SET STEP allowed me to do that as desired.
An approach that I have used when working on a method that is
called from a number of places that are not involved in what I am
doing is to use set step on, but only execute it when a debug flag is
set. I toggle the flag with an OKL. Something like:
Setup:
private debugflag
debugflag=.f.
on key label "alt-d" debugflag=!debugflag
Use:
if debugflag
set step on
endif
The OKL means that I can turn the debugging on and off as I
want in a form. If I want the singlestepping to be a one-shot, I can
add a debugflag=.f. just after the if debugflag statement.
Sincerely,
Gene Wirchenko
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
