New firmware version 4.0.17

[Link: pronto.philips.com]


Joe,

Yummie, yummie, looking forward to those features ;-)

Great! I haven't tried it yet.... I hope that the rotary wheel can be defined not to turn on the display when turned (particularly for devices that don't use the rotary wheel).

Support for IP cameras sounds interesting. I have 2 Panasonic web cams (which can server web pages or do ftp).

Nope, that functionality was not added, only a way to get clicks to detect motion.


In your activity, simply provide an onScroll function as follows:

onRotary = function(clicks)
{
// clicks = 0 upon rest
// else Positive clicks = number of clockwise clicks in last 100ms
// else Negative clicks = number of counter-clockwise clicks in last 100ms.
}

Corrected my function name. Not enough sleep and too much time working on a fully integrated Escient Activity.

V1.1 of the Developers Guide is also available in the installers area.

Sorry, my TSU9400 is still away (screen needs repair), so I can't test the new firmware. But do I understand the new functionality correct: You can only use the rotary wheel if you are able to use Pronto Script ?
Other way round: Can I program the remote to add an IR-Code to the scroll wheel using PEP like any other button ?
Probably not, because there is no new version of the editor...
Greetings,
Nocko!

Anyone care to speculate on why the 9400 firmware is 14Mb and the 9600 firmware is 20Mb?

The 9400 can't do wav files and has a lower screen resolution. So it would not have the sounds built in to the operating system for the 9600. There are very few images in the operating system (such as the start up screen). That does not explain a 6Mb difference.

Actually - in case anyone is excitedly programming without downloading the new prontoscript developer's guide - it's

onRotary = function(clicks) {}

(Stuck in a hotel with too much time on my hands and no 9600.)

Can the rotary dial be programmed to perform transport actions such as ffwd on clockwise and rwd on counter-clockwise?

If you so desire. You'd do this by checking +/- on clicks and then issuing executeActions() on a widget containing IR codes to do jog back/forward functionality.

See my immediate post above. Doing the ProntoScript for what you are asking is really pretty easy.

I read Lyndel's post on the scrolling action for the rotary wheel, I have never used prontoscript and no background in any of this stuff. I tried using his input in one device under advanced, but have no clue how to make the rotary wheel scroll thru pages. Sorry, it is probably very easy but I can't follow that stuff! Any Help

To make it scroll through pages, you should create 2 buttons in a page in your config using Page+ and Page- actions.

Then, invoke these widgets by retrieving them and calling executeActions() as needed.

The majority of the code is rather simple and after a read of the Dev Guide and practicing with the examples, you should be able to make sense of the above.

If you still need help, email me offline.

Hi CBD,
I am a beginner myself and I know how it feels. Start by practicing examples in Prontoscript developers’ guide.
Get "JavaScript: The Definitive Guide"-David Flanagan, it will help you.

Have a look at the code below:

onRotary = function(clicks)
{
if (clicks > 0)
{System.print ("ROTARY Right");
GUI.widget("PS_PAGE_UP").executeActions();
//CF.widget("RIGHT", "ACTIONS", "RESOURCES").executeActions();
}
if (clicks < 0)
{System.print ("ROTARY Leftt");
GUI.widget("PS_PAGE_DOWN").executeActions();
//CF.widget("LEFT", "ACTIONS", "RESOURCES").executeActions();
}
};

-------
This is to execute PageUp and PageDown when you rotate the wheel.
If you uncomment the other lines, it will execute actions (whatever you choose: rs232, ir, ) of buttons "LEFT" & "RIGHT", located in the page named "ACTIONS" in activity/device "RESOURCES", which of course you have to create.

I hope it helps, however it is more fulfilling if you discover/write it yourself :)

Sorin

Note that Sorin's example assumes that the Page +/- buttons will execute the Page Up/Down actions. This may not be the case in all activities (you've assigned your own actions to these keys).

That being the case, you'd create 2 buttons as I mentioned above and then use CF.widget() as Sorin suggests above to reference the 2 buttons.