I would recommend "a" - the event driven watch process. I think there are a couple of advantages, 1st - you'll get the event notification in pseudo "real time" - that is, the event will get to you, I would guess within a few hundred milliseconds of the change. The timer option would only be able to detect the change at the defined timer interval.
Further, your program (and Windows) will be interrupted to handler the timer events (messages) at even timer interval as long as the timer is active, taking away system resources from whatever else is running at the time. Good Luck
-------------- As a circle of light increases so does the circumference of darkness around it. - Albert Einstein
I'm with Cajun; the timer function approach advised by Debeast is hugely, hugely inefficient and a waste of resources, except under very finite circumstances.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.