Since upgrading to PEP 2.4.18 and the new firmware my scripts are no more working. I have a 9400.

1. Problem:

I haven a jump action on a firmkey (PS_FIRM5) and the following little prontoscript:

onHold = function()
{
label = "test";
executeActions();
};
onHoldInterval = 1000;

The label is set to text, but no Actions are performed.


2. I have actions on othe rfirmkeys and there is a different behaviour of the onHold function if i select the firmkey on the touch or i select the hard button.
Selecting the touchscreen onHold works fine, selecting the hard button nothing happens.

Any idea what they changed?

Thanks

otellodb

I was just about to post on this same problem (with my 9400) but my issue is intermittent (which I find even stranger). I think it has to do with how we are calling executeActions() (I use "this.executeActions()"). The only reason I think its this is because I have some soft buttons with issues that I am not using onHold, I'm simply checking some things and running "this.executeActions()".

I've found what they've added but not what they've changed and from the PS docs (and I haven't found anything in the Proto Certified site either). Does anyone have this? or maybe know what JavaScript engine and version they are using?

I should also note, my XCF was created in PEP2 and updated to every release since

I might have just figured it out. Try "scheduleActions();" instead. Found this in the guide:

Action lists can not be executed in parallel. This means that when a script calls the
executeActions() method while an action list is already being executed currently
an exception will be thrown.
When the calling script requires the action list to be executed, it is advised to use
scheduleActions() instead.

Calling executeActions() will not work from within a page script. This is due to
the restriction that the control panel cannot play multiple action lists at the same time
and a page script is always executed after a page jump action within an Actionlist. Again, scheduleActions() can be used instead, to avoid this problem.

Nothing better with "scheduleActions();" instead. NOthing happens even then.
I can start ececuteActions() with an widget on an other page fully quallified with Activity,Page,Widget. But actually no chance to start the local actions.

I created a new project with only this actions but nothing better.

Try this please:

onHold = function()
{
label = "test";
this.executeActions();
};
onHoldInterval = 1000;

I have the same issue.
these scripts will not work on the firm keys after I upgraded.

Definitly no chance with the firm keys. It works with buttons on the screen, but not possible for the firm keys even not with this.executeActions();
It works with other buttons correctly. Up to now there are only problems with PS_FIRM1 to PS_FIRM5.
Perhaps bug in firmware ??

One funny new thing. If you delete the corresponding button on the touch screen it works. I think definitly there is a bug.

On the FIRM1-5 enter the following (change the numerals) with an IR code followed by a jump to another page in the action list:


onHold = function()
{
label = "(F1)";
this.executeActions();
};
onHoldInterval = 1000;

onRelease = function()
{
label = "1";
}

In the simulator, while the Firm keys will not execute the jump (or throw an error), regular soft buttons will execute the jump (and throw an action list error). The label on the Firm keys will update as expected.

There are no Pronto's at this location, I can't try the above on a real remote.

The above was started as a new program for a TSU9400.

I think this is likely a bug. I have asked Belgium to investigate but it may take a while as CES is coming up and vacations are in progress as well.

I expanded and fussed with my program above on a TSU9400 and the executeActions() jump fails only on FIRM1-FIRM5. Soft buttons and all of the other hard keys work fine. I see the same response on the simulator.

Edit: same deal with scheduleActions() -- only the FIRM keys fail.