| Post 1 made on Monday January 12, 2009 at 13:38 | ...it's new! |
MrPUK Junior Member |
| |
I'm a little unsure how to do a Page flip in Pronto Script anyone have any ideas?
Cheers
Iain |
Mr P | [ Reply | Quote & Reply |
| Post 2 made on Monday January 12, 2009 at 14:39 | ...it's new! |
MrPUK Junior Member |
| |
| My bad, should have searched for Jump and not page flip, just looking at it now. But any points would be great. |
Mr P | [ Reply | Quote & Reply |
| Post 3 made on Monday January 12, 2009 at 18:37 | ...it's new! |
Jon Welfringer Long Time Member |
| |
| Put your jumps in a hidden button's actionlist and then call that list via script with executeActions(). |
| [ Reply | Quote & Reply |
| Post 4 made on Tuesday January 13, 2009 at 17:56 | ...it's new! |
Lyndel McGee Loyal Member |
| |
My suggestion is to also wrap your call to executeActions() with a try/catch block to prevent ActionListErrors from frequenting your diagnostic log.
Also note that if you are trying to do widget.executeActions to achieve a jump from a page script, you must wrap this call to schedule later using CF.activity().scheduleAfter() as documented in the Pronto FAQ on the Philips site.
Ian,
And since you mean Page Jump instead of Page Flip, why not edit your original post and change the subject line so a search for +Page +Jump +ProntoScript will pick up this post? |
Lyndel McGee
Philips Pronto Addict/Beta Tester
View EscientPronto 1.0.2 Docs - http://www.mediafire.com/do...hp?yyfzfzzok5z | [ Reply | Quote & Reply |
| Post 5 made on Tuesday January 13, 2009 at 18:09 | ...it's new! |
Jon Welfringer Long Time Member |
| |
| On Tuesday January 13, 2009 at 17:56, Lyndel McGee said... |
| Also note that if you are trying to do widget.executeActions to achieve a jump from a page script, you must wrap this call to schedule later using CF.activity().scheduleAfter() as documented in the Pronto FAQ on the Philips site. |
Wouldn't this only need to be done if you had additional commands to perform within the script? I've found that if I am aborting the script to do my jump that the executeActions jumps just fine and all processing continues as expected. |
| [ Reply | Quote & Reply |
| Post 6 made on Tuesday January 13, 2009 at 18:25 | ...it's new! |
GuerillaBuild Junior Member |
| |
A lot of times people put an executeActions() in the middle of their scripts and wonder why half of their script never processes or something just plain doesn't work. The big issue is that the script that contains the executeActions may be part of a chain of script functions. Thus what Lyndel is saying is defer your action list with scheduleAfter() such that all of your scripts process properly. In short executing actions while a script is running causes the script to bomb out and if memory serves may also bomb your actions. You can sometimes avoid a scheduleAfter() if your executeActions() is the last line of script to be executed during the current process.
You can see a similar issue with GUI.updateScreen(). If you change visibility on a widget or use GetImage() on a widget. You won't see the results until the script fully finishes. Sometimes this never occurs and sometimes it occurs well after the button push or event trigger. If you place a GUI.updateScreen() just after the 'change event' it executes immediately on receipt of the GUI.updateScreen() method. |
You can hide almost anything until you have to put the drywall up! | [ Reply | Quote & Reply |
