|
-
Apr 4th, 2000, 10:53 AM
#1
Thread Starter
New Member
The Internet Transfer Control's Execute method operates asynchronously. The StillExecuting property returns a True/False if there is currently a request pending.
If I was to code such:
Inet1.Execute "DIR"
Do While StillExecuting
DoEvents
Loop
DoEvents function allows the operating system to process events and messages waiting in the message queue, but what is happening? What is the DoEvents doing?
What I would like to achieve, I would stop all "continued" action until there isn't any request pending; making the method act synchronously.
Also any help with understanding DoEvents function and its purpose?
PLease any help?
Thanks,
deDogs
-
Apr 4th, 2000, 11:05 AM
#2
From my understanding of DoEvents, I think what it does is basically Does Events, it's that simple, Sometimes your program may something that may block other window events from happening for example, some people like to use the Sleep API function without using DoEvents... WHen you use Sleep, it puts windows into kind of a sleep mode (it doesn't do anything) for specific amount of time, and that could have some side effects for programs that are currently doing stuff, for example, you can say that there's a Virus Checker, Checking files in the background, it can temporarily stop doing what it's doing, and not function, or there could be a lot of other things that can happen. So you put DoEvents to tell Windows to Just put THIS ONE program into whatever it's doing and let every other program run on their own course... the Inet functions have usually nothing to do with other programs what so ever, it's not just your program, if you've used CuteFTP or WS FTP, you would've found out that when you give them a command, they won't respond to your other commands at all... may be I'm not getting what you're trying to say, but here's what I know about the DoEvents function..
-
Apr 5th, 2000, 04:18 PM
#3
Lively Member
With my experience with Inet and DoEvents I found that Inet was insisted on being a real pain in the a** so I ditched it and switched to raw sockets, yes, it is harder but...
a). You learn more with raw sockets
b). You have full control over input/output
c). You control the downloading...
My thoughts...
Regards,
 Paul Rivoli 
---------------------
[email protected]
http://members.dingoblue.net.au/~privoli
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|