Hey,

A made may first pronto-script. this for tracking a power toggle of a telenet digibox. But a git a error whit the executeActions(); line.

this is the error:
ProntoScript error: ActionList Error
Offending button script: (untagged)
Offending line #3: "CF.widget("TELENET_OFF","KNOPEN", "HOME").executeActions();"

this is may first pronto-script so its gone be something small. But a cant find what it is.

thx

ps.: sorry for may bad English...

Assuming this is a button script you need to use scheduleActions ....

delesh,

The 'ActionList Error' isn't actually an error, just a warning. Just ignore it - the action will execute fine.

I don't really understand why Philips don't suppress the warning - it is not actually warning of anything real.

ok, thx for the fast help. when a use scheduleActions, the error is gone. But when to use schedule or execute? In the manual it says a can use the two...

The difference between these two methods is that executeActions() will execute the actions
synchronously, resuming script execution only when the actions are completed. The schedule-
Actions() method however, will execute the actions in the background, and script execution
resumes immediately after invoking the scheduleActions() method.

But stile one gifs a error. But a don't git way

thx

Elsewhere in the manual it also says you can't have two button script handlers running at once:) Philips addressed this in a later firmware release by providing the scheduleActions method.

ok thx

and ind its in the manual. sorry for that... hahaha

The Prontoscript FAQ on Philips website also discusses issues with using executeActions() from inside a Page script.

One point to keep in the back of your mind is that each call to scheduleAction() and executeAfter() use the same (limited) timer resource. If one queues too many items (more than 10) there will be trouble. And, there are some interactions between the page timer and the execute[]() functions. I have not completely worked out what this interaction is and I suspect that it could change from firmware version to version.

I am hedging my bets by defining my own executeThis() function. In my function I can use scheduleActions() or executeAfter() or a more complex queuing function. If I change my strategy, I only need to modify my function, not track down every action in the the program.

Now I can use:

executeThis( this );

to execute the action list on the current button. This is very handy when one needs to execute a few ProntoScript statements, then execute a few IR commands and jump somewhere. Sending IR commands by ProntoScript can be problematic if one changes the device model. (Actually, I'm using constructs that behave like the old Link pages)

While the whole procedure requires some discipline, is a little abstract and contorted, it is possible to code devices that use quite a lot of ProntoScript to send IR (or RS-232, at the flip of a global) commands and jump around, but can be freely copied from program to program without breaking tag references.

I seem to recall that the limit has been upped to 64 from 10.