Hi all,

My TV has a power toggle button only and I can't find any discrete codes. If I switch Activities the TV is power toggled and of course I don't want that. I am trying to write a script by using a global variable which keeps the state of my TV.

The script below is working fine when the ACTIVITY_MACROS page is within the current activity but I don't want that. I have a "activity" called Macros where I keep all my macros but I can't find a way to execute buttons on pages outside the current activity.

I am also looking for a way to jump to pages outside the current activity to provide feedback to the user (eg. Please wait, system is being setuped).

Any help will be appreciated

if (System.getGlobal("power_toggle") == "off")
{
System.setGlobal("power_toggle", "on");
page("ACTIVITY_MACROS").widget("TV_POWER").executeActions();

page("ACTIVITY_MACROS").widget("WATCH_TV").executeActions();
}
else
{
page("ACTIVITY_MACROS").widget("WATCH_TV").executeActions();

}

I generally write the reference to the button as
CF.widget("WATCH_TV","ACTIVITY_MACROS").executeActions();

Sometimes I need the "CF" or sometimes "GUI", easy to try.

In general the reference is widget("ButtonTag","PageTag","ActivityTag"). ....
Leaving arguments out (starting from the right) defaults to current activity, current page. If Outside the Activity you might need the CF prefix as in CF.widget

Barry,

Thanks, You helped me on my way.
Do you also know how to program a jump ? (eg after power off I want to jump to the Home screen)


Thanks in advance

The way you do this is to code a 'Jump' in the ActionList of a widget and then issue 'executeActions' against the widget containing the jump. Be sure that you do this using ScheduleAfter as all scripts will end as soon as the Jump out of the activity is processed.

Here's an example to play with.

var w = CF.widget('GoHome','MyPage','MyActivity);
if (w)
CF.activity().scheduleAfter(10,function(x){try{x.executeActions();}catch(e){Diagnostics.log(e);}},w);

It is important to use try/catch here as you don't want to let any errors propagate out of your function as this could, in some cases, cause instability in the Pronto. It's not so much of a problem now as it was in earlier ProntoScript releases but it is always good practice to prevent errors from propagating out into the system from your own code.

thanks a lot !

You both are a great help