Page tracking question

adys

I have the same DVD in 5 differnt places, so I wanted to use the same screen.

But then I am loosing is the ability to save the statuses in the screen chanels...

What is your recomended way? to save the statuses in my program and to use the same screen or to use different screen for each instance so I can use the chanels to hold current buttons states?

(I am talking only about buttons states)


While checking and learning how to work with same page for all I found out that page tracking can help with this, I just can't find how to catch the page change event details..

What I want to do is to catch the load of the page and to update it with the right status for the specific instance. again, only if this is the right thing to do , maybe after all its better to duplicate the page?

Thanks for any help

Ady.

Joe Hebert

adys wrote:

While checking and learning how to work with same page for all I found out that page tracking can help with this, I just can't find how to catch the page change event details..

DATA_EVENT[dvTP] {

   STRING: {
      //catch page tracking messages here
   }
}

jjames

My suggestion would be to do manage your pop-ups and pages in code. I think the idea of managing your own popups to many may seem like a horrendous undertaking. It really isn't, and I feel should be the reccomended style of programming (they taught some of it in P2.) This way, you know exactly what is going on rather than depending on feedback to see what page the client is using.

What I do is write a function (or call) to handle my pop-ups, and do a SWITCH/CASE on the current source (a basic example is here somewhere on the forums). If you're panel has a central area where your sources are controlled, you put them into a "popup group" and they become mutually exclusive, so there really isn't much code to handle showing popups - just call out the popup you want up and current one closes. Doing this would also allow you to write a seperate function (or call) that would update the text on the page with much ease.

Just my two cents...

DHawthorne

I don't worry about page tracking, I track the source. In my feedback management, I use a SWITCH...CASE block to send the appropriate feedback for whatever device is currently being controlled, and likewise to send the appropriate commands on a button press to the correct device.

jjames

That's actually what I was trying to say. I do very little page monitoring, and mostly base all of my pop-ups on the current source. I will track whether the panel is in a certain "mode" so I can determine whether or not to send a volume popup page or not. But that's usually all I do as far as page tracking.

adys

Thanks

About my first question, what approach do you recommend?

I have same device in 5 diff rooms.
To hold 5 diff pages to save states in channels, or to use 1 screen and to hold states in code and update screen on load?

jjames

Hold the states in code and update as needed would be my suggestion. Cuts down on unnecessary traffic going to the panel. Plus it gives a foundation on an easily expandable system.