On the TSU9600 does anyone know how to program a page jump from a Prontoscript program?

For example, I am opening a TCPSocket on my custom page but when the user presses the Home button, I want to close the socket before the Home page is displayed. I can re-program the Home button to close the socket using Prontoscript but can't figure out how to get it to "jump" to the Home page afterwards.

Keep in mind that I'm not a programmer. That being said here is my best guess. Place a button on a hidden page. Said buttons action list should contain the needed "jump to" action. Give both the page and button ProntoScript names, then utilize the executeActions() method in your ProntoScript to execute the action list for said button. For more details reference page 25 of the ProntoScript Developer's Guide.

Lowpro is 100% correct. For not being a programmer, A+++.

:)

Also if you have debugging operating you will get an error message when the jump takes place, but that is intentional according to my Pronto team contact in that it is a reminder that the current script is about to abort. I guess if you can't fix it, feature it.

Lowpro, thanks for the suggestion.

I actually implemented the feature by:
1) Creating a hidden page
2) On the hidden page, calling a Prontoscript function placed in Device Properties
3) On Device Properties->Advanced, create the function to close the TCP socket
4) On Device Properties->Hard Buttons, deselecting Use System Page Actions then
Add Actions of:
a) Jump to the hidden page
b) Link to the Home page

What happens when I press the Home button when I am on my custom page is that I "see" the hidden page for a split second then the Home page is displayed. This is satisfactory even though it is not a "pure" Prontoscript solution.

Not sure what the hidden page is for but you can get the Home Hard Key with GUI.widget("PS_HOME") and then simply invoke executeActions() on this widget. When you do this, you will get the messages that Barry mentions above.

Lyndel

When the Home button is pressed, it will Jump to the hidden page. The hidden page has in its page script just a call to the function that closes the socket. Then it returns to the Home button script that links it back to the Home page.

I don't get the debug messages doing it this way.

The debug message is always generated on a jump using the executeActions method. You just do not see it if the debug page is not visible or does not exist. Since a hidden page has no visible widgets, the debug page's debug panel (_PS_DEBUG_) can never be seen, ergo no message to be seen.

Something like trees in a forest make no sounds when falling if there is no one around to hear.