Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Why do we need to call Refresh from Activate?
Message
 
 
À
Tous
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Titre:
Why do we need to call Refresh from Activate?
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows XP
Network:
Windows 2003 Server
Database:
MS SQL Server
Divers
Thread ID:
01415415
Message ID:
01415415
Vues:
114
Hi everybody,

I'm debugging weird issue in my project. I had perfectly working form and the application. Then for a moment I switched to a different task, another developer took control and now the form that worked perfectly is broken.

This is VPM based application. Debugging it is absolutely no fan, because there is tremendous amount of code called from each method.

Anyway, right now it seems to be down to calling Refresh from the Activate (the problem somehow lies in the Refresh method of this form).

However, my question is - why do we need to call Refresh of the form from the Activate of the form at all? Do you see any hidden sense in it?

And if there is no sense, is there a way to prevent Refresh if it was called the first time from the first Activate?

Thanks in advance.

Turned out I made such a mistake - it's even embarrassing to tell. Instead of the click event of the new button I added recently I put code into the Refresh method. Took me very long time to find it.
If it's not broken, fix it until it is.


My Blog
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform