Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
What do you mean 'not responding'? Busy!
Message
De
24/01/2015 10:11:49
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
 
 
À
23/01/2015 13:31:02
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2003
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01614202
Message ID:
01614273
Vues:
70
>Did you look into offloading the "Busy" work to another thread or a special worker process ? PoolManager from vfp6 days spawned ideas and some code, probably the latest and most used on current OS and latest vfp being ParallellFox...

Looked and decided I won't kill an ox for a kilo of meat. This is not really a problem, just an annoyance.

The point here is that I have a simple/single .prg which I run from a command window, may interrupt it at times, need to check for errors - I log them but echo log to _screen so I see them right away. Then edit, run again... as simple as looking at the log, modi comm convblabla, do convblabla... And if Microsoft didn't decide that every piece of code should respond every few seconds to this tap on the shoulder, it would have run just like before. And I didn't mind the "not responding" being added to the _screen.caption - it's the blanking of _screen and any other window in it that's annoying. I don't see anything, the wait window window doesn't paint anymore, the _screen is white on white, my echoed log is invisible. That's the kind of interference by the OS that I don't like.

More annoying - it worked fine before, it wasn't broken, yet they had to fix it.

back to same old

the first online autobiography, unfinished by design
What, me reckless? I'm full of recks!
Balkans, eh? Count them.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform