Sub Main()
Gridscreen()
End Sub
Sub Gridscreen()
port=CreateObject("roMessagePort")
grid=CreateObject("roGridScreen")
grid.SetMessagePort(port)
rowTitles=CreateObject("roArray",10,TRUE)
For j=0 To 10
rowTitles.Push("[Row Title "+j.toStr()+" ] ")
Next
grid.SetupLists(rowTitles.Count())
grid.SetListNames(rowTitles)
For j=0 To 10
list=CreateObject("roArray",10,TRUE)
For i=0 To 10
o=CreateObject("roAssociativeArray")
o.ContentType="episode"
o.Title="[Title"+i.tostr()+"]"
o.ShortDescriptionLine1="[ShortDescriptionLine1]"
o.ShortDescriptionLine2="[ShortDescriptionLine2]"
o.Description=""
o.Description="[Description] "
o.Rating="NR"
o.StarRating="75"
o.ReleaseDate="[<mm/dd/yyyy]"
o.Length=5400
o.Actors=[]
o.Actors.Push("[Actor1]")
o.Actors.Push("[Actor2]")
o.Actors.Push("[Actor3]")
o.Director="[Director]"
list.Push(o)
Next
grid.SetContentList(j,list)
Next
grid.Show()
While TRUE
msg=Wait(0,port)
If type(msg)="roGridScreenEvent"
If msg.isScreenClosed()
Exit While
Else If msg.isListItemFocused()
Print"Focused msg: ";msg.GetMessage();"row: ";msg.GetIndex();
Print" col: ";msg.GetData()
Else If msg.isListItemSelected()
'problem is caused by this, or any combination of springboard screen on top of gridscreen, etc etc
audioPlayer=CreateObject("roAudioPlayer")
audioPlayer.SetMessagePort(port)
item=CreateObject("roAssociativeArray")
item.Url="" '''any item can go here, makes no difference if it's a valid url or not
item.StreamFormat=("mp3")
audioPlayer.AddContent(item) ' this is the problem line to screw up the gridscreen display
Print"Selected msg: ";msg.GetMessage();"row: ";msg.GetIndex();
Print" col: ";msg.GetData()
Else If msg.isRemoteKeyPressed()
Print"Button Pressed msg: ";msg.GetIndex()
End If
End If
End While
Return
End Sub
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!