Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Possible interferance from a timer?
Message
De
02/08/2012 10:10:37
Thomas Ganss (En ligne)
Main Trend
Frankfurt, Allemagne
 
 
À
02/08/2012 09:54:18
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Versions des environnements
Visual FoxPro:
VFP 8 SP1
OS:
Windows 7
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01549560
Message ID:
01549819
Vues:
40
still nothing as plausible as the rdpclip....
How "reliable" is getting the hang in at least one machine in 3 days running?
Are those machines bolted tight against user stupidity ?

If answer is in the realm of "pretty good", first I'd try shooting in the dark with a C++ timer (around here somewhere)
***after*** adding either coverage or logging - depends on how much data is gererated.

update:
move the timer action code away from interacting with your forms, displyaing the time info in
wait window nowait noclear
for test purposes a couple of days if possible. /update


Then move all similar code into calls in other ***proccesses***, if possible
- automating a player if such is available (never looked if one sports an interface)

>The only thing I can think of is that the 2nd screen is the Listening portion of the test, which makes a call to the Windows Sound Player with
>Declare Integer sndPlaySound In winmm;
> STRING lpszSound, Integer fuSound
>
>and the call is:
>
> = sndPlaySound(WavFileName, SND_SYNC + SND_NODEFAULT)
>
>timer interval is 1000
>
>>drat...
>>activate your logging module, run under coverage and/or sprinkle in doevents
>>any activeX / OLElinking working ?
>>timer interval ?
>>
>>>No, no rdpclip.exe task running.
>>>
>>>The timer is on the form in conjunction with a label to act like the clock. The timer event code is as follows:
>>>
>>>
>>>if Thisform.lblTime.Caption <> time()
>>>  Thisform.lblTime.Caption = time()
>>>endif
>>>
>>>
>>>>>On some machines (this morning, it was 4 out of 14) after the first Listening question, the (blank) Reading form comes forward and the application is locked up.
>>>>>
>>>>>Any ideas as to why this is happening? This is a little crazy-making.
>>>>
>>>>Swag:
>>>>If you have manual access to the HW, load task manager, look for a rdpclip.exe task.
>>>>If this is running, kill it - and look if your app is still locked up.
>>>>
>>>>If not, describe what the timer does -
>>>>from description I get the impression getting time into a property might be sufficient.
>>>>
>>>>regards
>>>>
>>>>thomas
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform