Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
How could this be
Message
De
12/03/2003 10:51:45
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Programmation Orientée Object
Divers
Thread ID:
00764327
Message ID:
00764826
Vues:
22
Ron,

Does it still misbehave if you remove the oForm = newobject() line, and take oForm out of the picture?

>>>cFrmDetailListing absolutely does not call back to THISFORM and change THISFORM.lIsOkToSave
>>>
>>>What am I missing here.
>>>
>>>
>>>
>>>* Evaluates to .F.
>>>WAIT WINDOW '1: ' + IIF(THISFORM.lIsOkToSave, 'T', 'F')
>>>
>>>oForm = NEWOBJECT('cfrmDetailListing',    ;
>>>                  'MCSForms_DetailInput', ;
>>>                  NULL,                   ;
>>>                  cProvider)
>>>
>>>*Still .F.
>>>WAIT WINDOW '1: ' + IIF(.lIsOkToSave, 'T', 'F')
>>>
>>>IF VARTYPE(oForm) = 'O'
>>>      WITH oForm
>>>         .SHOW(1)
>>>         WAIT WINDOW '2: ' + IIF(THISFORM.lIsOkToSave, 'T', 'F')
>>>
>>>         IF .lSelected
>>>            cRetVal = .cCode
>>>            THISFORM.cPCAdd = '4'
>>>         ENDIF
>>>
>>>         * All of sudden true and remains .t. when it should not be.
>>>         * should be .f.
>>>         WAIT WINDOW '3: ' + IIF(THISFORM.lIsOkToSave, 'T', 'F')
>>>
>>>      ENDWITH
>>>ENDIF
>>>
>>>
>>
>>Do you have any Access or Assign code on the .cPCAdd property?
>>
>>Try setting a breakpoint in the debugger on your property and see exactly who is changing it.
>
>
>When I step through in Debug it works as intended. Although I do use access and assign I am not here. Already checked that.
Steve Gibson
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform