quote:
Originally posted by Itsme-HcK
That will make my plug-in run all the time, while it is only supposed to be called once in the <number> minutes...
Your plugin (or at least a process of your plugin) will indeed always run. There is no way around in (in whatever language) as that is exactly what a timer does; it constantly needs a process to run, the process of the timer (what the timer process calls when it fires is another matter, that process doesn't need to be run all the time)...
Calling an external DLL for this is not better. True, you could do that, but even then a process needs to be running all the time. So why call an external process (with all the disadvantgaes of syncronization, or detecting when it needs to end, or whatever) while you can do this from your plugin itself (with the advantage that you have far less troubles, if not none, with syncronizations, etc), and above all, it already runs all time anyways...
quote:
Originally posted by Itsme-HcK
Err, read what I said again. 
I will have to parse the MSG's. (Which forces me to run the whole time.)
you parse messages (or whatever you want) in the TimerProc. TimerProc is only fired/called when a timeout occurs.
EDIT: damn, J-Thread was first
(I always say refresh a thread before replying, but I often forget to do that also)
/ 
