Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Tip of the Day
Message
 
À
19/10/1999 08:45:12
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Titre:
Divers
Thread ID:
00278095
Message ID:
00278106
Vues:
16
Only after it's own .Activate() fires, right after .Init()

One of the things I use it for - to get the calling form datasession ID if I need to.

lnDatasessionId = _screen.activeform.DataSessionId

>Nice tip, Nick. So when exactly does the child form become the active form?
>
>
>>When you run one form from another, in Init() of child form you may access the properties and methods of the parent form directly without passing the parameters - i.e
>>
>>thisform.someProperty =_screen.activeform.myProperty
>>or
>>thisform.someControl.Value =_screen.activeform.someControl.Value
>>
>>This is based on the fact that when the child form is in its .Init() it is not an activeform yet, because its .Activate() didn't fire so far, so the calling form still stays active at this time.
>>
>>Nick
Nick Neklioudov
Universal Thread Consultant
3 times Microsoft MVP - Visual FoxPro

"I have not failed. I've just found 10,000 ways that don't work." - Thomas Edison
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform