Hi,

first I want to tell you good news (I hope they are new for you;) )

With the new firmware 7.2.2 ProntoScript is enabled on TSU9300 !!! I also recognized that now the Firmware for 9300 and 9400 are absolute identical!

In release notes they mentioned that now the usage of gestures are now supported in scripts. Has anybody tried this already. How does this work?

Regards
  Duddits

It will let you load scripts but it does not seem to run them :(

Did you run a search for Gestures in this forum? The Gestures are accomplished through use of the onPress, onMove and onRelease callback notifications now available to Widgets (you can assign your own functions) as documented in the Dev Guide. Basically, when you press a button, you can capture the coordinates and when you move your finger on the screen, you can get onMove() notifications that allow you to reposition the widget to follow your finger.

There is a link in the release notes on Philips' site. It points to a configuration file that demonstrates new text capabilities. I suspect that this file may also have examples of coding up Gestures in a Prontoscript library contained within.

Here's the link. You will likely have to login to Philips' site to download it though.

[Link: 89.234.30.160]

The Philips site does have some example scripts but, IMO, they are much more complicated than they need to be and are certainly not a good basis for learning how to do gestures.

I just ordered a TSU9300. I'm upgrading from a TSU9200.

So does the 9300 now support scripts or not? I'm programming the remote before I get it, but don't want to waste a bunch of time on scripts if it won't run them.

No :(

I've heard rumors about ProntoScript being enabled on the TSU9300 in the future... Does anyone know more?

yes..............







its just a rumor :)

Does anyone know if we are going to be able to add prontoscript labels to grouped objects in the next software update???

pull out menu's would be kinda cool without having to animate them all.

also below is the working script from the visualdemo for movable buttons

drop it into the page script box, Label the Page prontoscript name TEST and the button on that page you want to move B1


/*global
GUI:false
CF:false
System:false
*/
/*jslint
forin:true
*/

(function () {

function buttonPress(x, y)
{
this.lockInfo.pressX = x;
this.lockInfo.pressY = y;
this.lockInfo.x0 = x;
this.lockInfo.x1 = x;
this.lockInfo.x2 = x;
this.lockInfo.y0 = x;
this.lockInfo.y1 = x;
this.lockInfo.y2 = x;
this.lockInfo.pressed = true;
}

function motion(x, y)
{
var left, averageX,
top, averageY;

// Perform some filtering on motion events
if ((x < -10) || (x > 10) || (y < -10) || (y > 10)) {
this.lockInfo.x0 = this.lockInfo.x2;
this.lockInfo.x1 = x;
this.lockInfo.y0 = this.lockInfo.y2;
this.lockInfo.y1 = y;
} else {
this.lockInfo.x0 = this.lockInfo.x1;
this.lockInfo.x1 = this.lockInfo.x2;
this.lockInfo.y0 = this.lockInfo.y1;
this.lockInfo.y1 = this.lockInfo.y2;
}
this.lockInfo.x2 = x;
this.lockInfo.y2 = y;
averageX = (this.lockInfo.x0 + this.lockInfo.x1 + this.lockInfo.x2) / 3;
averageY = (this.lockInfo.y0 + this.lockInfo.y1 + this.lockInfo.y2) / 3;
if ((averageX > -2) && (averageX < 2) && (averageY > -2) && (averageY < 2)) {
return;
}

left = this.left + averageX - this.lockInfo.pressX;
top = this.top + averageY - this.lockInfo.pressY;
if (left < 0) {
left = 0;
}
if (left > (GUI.width - this.width)) {
left = GUI.width - this.width;
}
if (top < 0) {
top = 0;
}
if (top > (GUI.height - this.height)) {
top = GUI.height - this.height;
}
this.left = left;
this.top = top;
}

function buttonRelease()
{
this.lockInfo.pressed = false;
}

function init()
{
var homePage = CF.activity().page("TEST");
[ "B1" ].forEach(function (aTag) {
var arrow;
System.print("Configuring " + aTag);
arrow = homePage.widget(aTag);
arrow.onPress = buttonPress;
arrow.onRelease = buttonRelease;
arrow.onMove = motion;
arrow.lockInfo = {};
arrow.lockInfo.pressed = false;
arrow.lockInfo.x0 = 0;
arrow.lockInfo.x1 = 0;
arrow.lockInfo.x2 = 0;
arrow.lockInfo.y0 = 0;
arrow.lockInfo.y1 = 0;
arrow.lockInfo.y2 = 0;
});
}
init();
}());

I doubt that you will ever be able to apply a single ProntoScript name to a set of widgets in a group. You must write code to manage set of widgets as a group.

Just curious as to why you did not start new thread for this question vs posting deep inside thread about gestures. Makes searching very difficult as the topic of the thread has no resemblance to your question.

to me the idea of pull out menus is a gesture driven activity, hence the post i searched gestures came up here read the thread and commented also lyndel as it says its was my first day!!!!!

wont do it again promise!!!! :-)

Anderson,

Was not intending to beat you up. My sincerest apologies. Welcome on board. FYI, there's a thread around here somewhere that contains things that folks would like to see as new features.

BTW, thanks for the working code.

Is ProntoScript supported on TSU9300 after the 7.3.3 firmware upgrade? The North American Philips telephone support claims that it is. Is this really the case?

Thanks!

Still NO :)

OK, thanks! I've also found it in PEP2 (2.4.23) help: ProntoScript and IR with frequencies above 500 kHz do not work on TSU9300. I wonder if this is a PEP2 limitation and if PEP3 is going to bring any relevant changes - we'll hopefully see it soon enough.