ECS-L Home Automation and Security Archives
  learn more | view messages for this month | NetBloc® | terms of use | search

Google
 


  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects

Subject:
From:
Date:
Re: [ECS] General Questions
Don Stephens
Wed, 1 Mar 2000 15:59:12 -0800
Wed, 1 Mar 2000 15:59:12 -0800
Jeese A.J. Is that all?:-)
I will address the first issue, Mark will probably speak to the rest. The timer issue
is pretty straight forward...If you have two event controlled by the same timer, then
one of the two will probably do bad things. A timer set by one event, is cheerfully
counting down when another event resets it. You get the idea. I've got quite a few timers,
and aside from trying to remember what they all do, it hasn't been a problem.
Don
  ----- Original Message ----- 
  From: A.J. Griglak 
  To: ECS List 
  Sent: Wednesday, March 01, 2000 3:49 PM
  Subject: [ECS] General Questions


  -Is it necessary to use specialized counters, timers, and numbers for each event?
 For example, if the generic [Second-timer] is being addressed in two separate events
at the same time, what happens?
   
  -Is it considered bad programming to have multiple events triggered at the same time?
 Would this cause problems, for example, if two WPDLs are executed at the same time?
   
  -Is there a point where there are too many Events for ECS to handle?  Example - should
logic be near the top of events that does a Event-Exit if that Event isn't necessary
in order to streamline the code?
   
  -Is there a limit to the length of a single Event?  Or, should a 400+ line Event be
broken up into separate events (if possible)?
   
  -Is it OK to shut down Windows without closing ECS first?  Similarly, what happens
to the ECS files if the computer hangs and only a cold boot will work?
   
  OK, that's enough for now   ;-)
   
  -=A.J.


Jeese A.J. Is that all?:-)
I will address the first issue, Mark will probably speak to the rest. The timer issue is pretty straight forward...If you have two event controlled by the same timer, then one of the two will probably do bad things. A timer set by one event, is cheerfully counting down when another event resets it. You get the idea. I've got quite a few timers, and aside from trying to remember what they all do, it hasn't been a problem.
Don
----- Original Message -----
From: A.J. Griglak
To: ECS List
Sent: Wednesday, March 01, 2000 3:49 PM
Subject: [ECS] General Questions

-Is it necessary to use specialized counters, timers, and numbers for each event?  For example, if the generic [Second-timer] is being addressed in two separate events at the same time, what happens?
 
-Is it considered bad programming to have multiple events triggered at the same time?  Would this cause problems, for example, if two WPDLs are executed at the same time?
 
-Is there a point where there are too many Events for ECS to handle?  Example - should logic be near the top of events that does a Event-Exit if that Event isn't necessary in order to streamline the code?
 
-Is there a limit to the length of a single Event?  Or, should a 400+ line Event be broken up into separate events (if possible)?
 
-Is it OK to shut down Windows without closing ECS first?  Similarly, what happens to the ECS files if the computer hangs and only a cold boot will work?
 
OK, that's enough for now   ;-)
 
-=A.J.

  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects




Services provided by [NetBloc]®! NetBloc Solutions Inc.
Terms of use. Indexing software (c) 1999 Lin-De, Inc
.