Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Debugging a form
Message
De
24/01/2009 11:03:26
 
 
À
24/01/2009 10:59:50
Jay Johengen
Altamahaw-Ossipee, Caroline du Nord, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
01376719
Message ID:
01376730
Vues:
18
>>>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?
>>
>>I can't see this behaviour.
>>
>>Have you set breakpoint "on change" ?
>>Set it "on true"
>
>As you Resume from the debugger, you do not ever see the (Expression could not be evaluated) in the Watch window? I most certainly do. And if I have a breakpoint on that variable, it will stop the code.
* set lcMyVar = 'pippo' to breakpoint exp on true

t1()

T2()

PROCEDURE t1
	LOCAL lcMyVar

	lcMyVar = 'fabio'

	lcMyVar = 'pippo'
	* break here only !
	T2()
ENDPROC

PROCEDURE T2

='try'
='try'
='try'

ENDPROC
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform