Developers

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
maestorme
Visitor

Roku Screensaver Input

I'm trying to make a screensaver at the moment and I wanted to know how we can capture the key that was used to end the screensaver session.
Loosely trying to simulate what Roku does with the Magic City Scroller where you can press the play/pause button on certain billboards to directly go to that program in the channel.

Thanks!
Tags (1)
0 Kudos
3 REPLIES 3
necrotek
Roku Guru

Re: Roku Screensaver Input

I don't think you can get key presses during a screensaver. Look at the screensaver documentation here https://developer.roku.com/docs/developer-program/media-playback/screensavers.md. check out the section "Sharing active data"  As the billboard scrolls onto the screen, set a flag in the registry or temp file. In your channel you can check for this registry or file and act on that or set up rodeviceInfo "EnableScreensaverExitedEvent".
Tags (1)
0 Kudos
maestorme
Visitor

Re: Roku Screensaver Input

@necrotek thanks for your reply! I see what you're saying. That seems like an effective method. But even if I set a flag in the temp file, how will I know what button was pressed? For example, if it was any other button other than the play/pause button I wouldn't want to do anything.

Also, I couldn't find any documentation about EnableScreensaverExitedEvent. Is there a link you could point me to?

Thanks again!
Tags (1)
0 Kudos
squirreltown
Roku Guru

Re: Roku Screensaver Input

I believe Roku has not yet exposed that billboard trick to us peons.
Screensavers run in their own thread, so the only way to swap any kind of data is write it to the registry, so the screensaver or the channel could read it.
Kinetics Screensavers
Tags (1)
0 Kudos
Community is Being Upgraded!

We’re upgrading Roku Community to bring you a faster, more mobile-friendly experience. You may notice limited functionality or read-only access during this time. Read more here.

Planned Downtime:
Community will be unavailable for up to 24–48 hours during the upgrade window during the week of May 19th and you may notice reduced functionality. In the meantime, for additional assistance, visit our Support Site.

We're sorry for this disruption — we’re excited to share what’s next!