Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Consequences of AlwaysOnTop = .t.
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00483374
Message ID:
00485676
Vues:
11
I see. I'll take your word for it :)

>Thank you John. However the problem with wontop() and _screen.activeform occur when running code outside of the defined form. Please add the following to myprg:
>
>************
>Add Object cmdSuspend AS commandbutton WITH ;
>caption = "Suspend", ;
>left = 50, ;
>top = 120, ;
>height = 25
>
>Function cmdSuspend.Click
>suspend
>EndFunc
>
>*************
>
>Run myprg, hit the Suspend button, and from the command window enter:
>activate screen
>?wontop()
>?_screen.activeform.name
>
>wontop() will be empty, and _screen.activeform.name will give an error.
>
>Now, change alwaysontop to .f. in myprg and repeat. No problems.
>
>The problem occured in a project I inherited that had several alwaysontop forms, and some code like _screen.activeform.release() in the support class and prgs. There are work arounds, but I was surprised to run into this undocumented feature.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform