if type(msg) = "roSpringboardScreenEvent" then
if msg.isScreenClosed()
print "Screen closed"
exit while
else if msg.isRemoteKeyPressed()
print "Remote key pressed"
if type(msg)="roSpringboardScreenEvent" then
if msg.isbuttonpressed() then
ndx=msg.getindex()
if ndx=0 then
?"button number: ";ndx;" pressed"
else if msg.getindex()=1 then
?"button number: ";ndx;" pressed"
end if
else if msg.isremotekeypressed()
key=msg.getindex()
?"Key Number: ";key;" Pressed"
end if
end if
"agmark" wrote:
Is the info (*) button available on any screen other than an imagecanvas?
"agmark" wrote:
Thanks Chris. Tried isListItemInfo() on roPosterScreen and it responds. That's where I'll use it. I don't have a Roku1, but I assume the info button is strickly Roku2?
"RokuChris" wrote:
The (*) button works with any Roku since firmware 2.7. See section 2.4 of the Component Reference.
"belltown" wrote:Network remotes like Remoku, DVPRemote or the official Roku app (among others) have it and will work with any generation Roku. I frequently recommend the use of a network remote to early Roku1 owners when they ask how to re-arrange channels in the general discussion forum. It's probably not a good idea to code any critical functionality to the star/info button if you plan for a channel to be available to those models lacking the button(since most users probably won't go looking in the forum for the answer), but if it's a less-important or infrequently used feature it's probably ok to use it; another option is to also offer the same functionality via some on-screen menu or another button. Just some fyi opinion for anyone coming across this thread. 🙂"RokuChris" wrote:
The (*) button works with any Roku since firmware 2.7. See section 2.4 of the Component Reference.
... assuming you have a (*) button. My Roku 1 remote does not have an info or (*) button.
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!