| ECS-L Home Automation and Security Archives |
| Subject: From: Date: | RE: [ECS] Problem using Type Touchscreen-K Nathan Brown Tue, 12 Dec 2000 10:38:36 -0800 |
Kevin, I am currently using the Leopard with ECS and have had success running things in a mixed more for a couple weeks now, but it was a headache getting there. All my basic navigation control is in the Leopard with the major logic, text, and commands going to ECS. I found it usefull to have several "generic" screens that ECS can use to write information. For example, screen 15 has nothing but a "Done" button in the lower right. ECS uses this same screen for displaying Caller ID info as well as all General alert messages. I made an event in ECS that builds this screen based on the values of several text items. Then just call those events when a triggering event occurs, ie. telephone rings. Nathan -----Original Message----- From: Mark Gilmore Sent: Tue 12/12/2000 7:44 AM To: ecs-list@netbloc.com Cc: Subject: Re: [ECS] Problem using Type Touchscreen-K I don't know, but the LEOPARD should support both internal and external control concurrently. -- Mark Gilmore Omnipotence (ECS home automation software) http://omnipotencesoftware.com 423-745-0026 Hours: Mon-Sat, 9AM-8PM/EST Kevin Trainor wrote: > > Mark: > > 2. My three lines of code in the Leopard were the only ones that I have > ever written. So, I may easily have made a mistake. > > 3. Do you think that most people are doing screen-to-screen navigation on > the Leopard using direct ECS control. I would imagine that if you used > Ocelot/Leopard code to control navigation that it would be a bit quicker and > give the user a crisper response. On the other hand, if you can't mix the > two modes of navigation, then, it is probably just another novel recipe for > disaster. What do you think that most ECS Leopard users are doing on this > issue? > > Kevin > ----- Original Message ----- > From: "Mark Gilmore" <omnip@usit.net> > To: <ecs-list@netbloc.com> > Sent: Tuesday, December 12, 2000 8:27 AM > Subject: Re: [ECS] Problem using Type Touchscreen-K > > > Kevin, > > Are we saying that the LEOPARD will not respond to > > an ECS command(s) if it has it's own programming ? > > Sounds like a problem for ADI. > > BTW, you did not state if ECS was reporting an error message. > > -- > > Mark Gilmore > > Omnipotence (ECS home automation software) > > http://omnipotencesoftware.com > > 423-745-0026 > > Hours: Mon-Sat, 9AM-8PM/EST > > > > > > > Kevin Trainor wrote: > > > > > > I am pleased to say that I solved that problem by deleting the minimal > > > amount of event code that I had put into the Leopard. Now, I seem to > > > have full control of the Leopard from ECS. > > > > > > The small amount of event code that I originally loaded into the > > > Leopard was to get the Leopard to bring up Screen 1 whenever it > > > powered up. Now, I am directing the Leopard to Screen1 via ECS > > > command in my Startup event. Has anyone had luck in using native > > > Leopard/Ocelot code to control the default screen on the Leopard while > > > doing the rest of the navigation with commands from ECS? > > > > > > Kevin > > > > > > ----- Original Message ----- > > > From: Kevin Trainor > > > To: ecs-list@netbloc.com > > > Sent: Monday, December 11, 2000 9:44 PM > > > Subject: [ECS] Problem using Type Touchscreen-K > > > > > > All: > > > > > > I am using ECS Version 4.4.013. > > > > > > I just got a Leopard and I'm trying to interact with it via > > > the Touchscreen-K type. > > > > > > I seem to be able to sense button presses on the Leopard > > > quite well when I test the state of the relevant item. > > > > > > However, I don't seem to be able to get the Leopard to > > > switch to another screen by setting the item to the screen > > > number. > > > > > > Can anyone think of what I might be doing wrong? > > > > > > Thanks. > > > > > > Kevin > >