|
ECS-L Home Automation and Security Archives |
learn more
| view messages for this
month | NetBloc® | terms of use | search
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects
Subject: From: Date: | Michael's lockup Mark Gilmore Thu, 04 May 2000 16:52:13 -0400 |
Does anyone have a theory on what could "eat" Win TIMER messages ?
ECS sets a Win timer to .25 seconds, and then sleeps until
it receives a message. When the timer msg is received, it
executes Events and resets the timer.
The problem is that Michael's old lockup has returned,
whereby ECS occassionally freezes until he moves the mouse.
This triggers a Win message, which then "wakes up" ECS.
The lockup means that ECS never received the timer message.
The reason it is happening again is that I used an improved
method of coding around the problem, whereby I used a SECOND
"insurance timer" (ASSUMING that ONE would "get thru").
But apparently, this timer is being "killed" as well as the 1st.
???????
--
Mark Gilmore
Omnipotence (ECS home automation software)
http://www.usit.com/omnip
423-745-0026
Hours: Mon-Sat, 9AM-8PM/EST
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects