Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
LockScreen in Init()
Message
De
06/10/1997 08:26:04
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00052949
Message ID:
00053382
Vues:
32
>>Is it really faster to have LockScreen in the form Init() event to .T. while processing that event?
>>
>>I have this in my baseform. I set it to .T. at first and set it to .F. at the end of the Init(). During the Init(), the form is not shown, so I was wondering if there is really a need to have it there.
>
>Just as a comment, I do use .LockScreen, but I've never put it in the .Init() event. Plus, I've found that .LockScreen doesn't really get rid of "screen flicker" or whatever you want to call it so even wonder about it's value at all.

The only time I had to do a workaround in order to avoid a screen flicker is when I have some grids which contains some relational controls like combos. When this is the case, the form Refresh() is called after the Activate() event. What I did is to move the form to -2000 and bring it back in the GotFocus() event.

I replaced the relational combos with a view and the screen flicker is gone. It was then able to remove the -2000 code.
Michel Fournier
Level Extreme Inc.
Designer, architect, owner of the Level Extreme Platform
Subscribe to the site at https://www.levelextreme.com/Home/DataEntry?Activator=55&NoStore=303
Subscription benefits https://www.levelextreme.com/Home/ViewPage?Activator=7&ID=52
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform