Information générale
Catégorie:
Gestionnaire d'écran & Écrans
Versions des environnements
Network:
Windows 2008 Server
>>>>>Did you try to capture a coverage log. SET COVERAGE TO log.txt ? Then you can identify whether some unexpected code is run which is responsible for the delay?
>>>>
>>>>I had already searched for problematic code inside the various destroy events. I now did a SET COVERAGE and it revealed no special time consuming place. But more interesting is that it does not show the details of the native closing process at all!
>>>
>>>SET COVERAGE will only log VFP code and no internal processes.
>>
>>SET EVENTTRACKING is what should be used.
>
>Ah, this one indeed gives the time info of the destruction. But still not found the all explaining piece of code.
uniform or exponential times ?
Précédent
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement