Roku Developer Program

[jbrave]

I could have sworn in a previous firmware version you had to actually listen for keypresses on the messageport in order to to know if the user wanted to terminate a screen saver. It seems that any keypress now kills the screensaver. I was hoping to make an interactive screensaver...

-Joel

[TheEndless]

As far as I'm aware, the screensaver has always died on any keypress. If that weren't the case, then someone could potentially write a screensaver that locked up the box (except on home), which could be very confusing for the end user.

[renojim]

I believe the same thing as Endless. I think all of my screen savers have a 'while true' loop that there's no way to exit and obviously they all die when a remote button is pressed.

-JT

[destruk]

"jbrave" wrote:
I could have sworn in a previous firmware version you had to actually listen for keypresses on the messageport in order to to know if the user wanted to terminate a screen saver. It seems that any keypress now kills the screensaver. I was hoping to make an interactive screensaver...

-Joel

Wouldn't this be the same as a screensaver that isn't a screensaver? That sounds simple enough - simply have the end user disable the screensaver in the main menu settings and there you go.
Or you could do something really neat - license Dragon's Lair, (the laserdisc game) and have it stream sections/clips for the whole game for your screensaver. That way the internal screensaver will never turn on and it would be interactive just like you wanted. 🙂