Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Debugging a form
Message
From
26/01/2009 06:07:41
Lutz Scheffler
Lutz Scheffler Software Ingenieurbüro
Dresden, Germany
 
 
To
24/01/2009 10:13:57
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
01376719
Message ID:
01376975
Views:
12
>When Tracing through a form, it is very annoying that when you put a breakpoint on a variable - like lcMyVar = 'MyVarValue' - and the variable goes out of scope (Expression could not be evaluated) that it breaks. Is there anyway to exclude that condition and only have it break if the value has a value and it is different than what you are looking for?

You might create something with the "Break when expression is true" type of breakpoints

-store current value to an extra var
-create an breakpoint via menu, type "Break when expression is true2
-Expression: Storage#Variable and PROGRAMM(PROGRAMM(-1))="YOUR_CURRENT_PROGRAMM"
OR
--Expression: Storage#Variable and PROGRAMM(-1)=n" where n is the current return of PROGRAMM(-1)

this fires only if the var is changed in the program(level)

Agnes
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Previous
Reply
Map
View

Click here to load this message in the networking platform