Of course suspend/resume can't make the thread go to it's starting
point - too much state information could be messed up (registers,
stack, state of various "objects" like files or whatnot). Destroying
and recreating the thread might be okay, but there is some overhead
to this. You could use an EVENT object and make your thread wait
for that at the start of the threadproc, and have your main app
signal the event whenever the thread should have a go (use automatic

i'm failed at it.
Posted on 2011-04-17 02:08:22 by dcskm4200
invoke	CreateEvent,NULL,TRUE,TRUE,NULL

it's ok.
Posted on 2011-04-17 06:23:20 by dcskm4200