I've got an roGridScreen that shows when my app launches, which goes to an roPosterScreen, and then that goes to an audio player (built off of the audio player demo app). When I visit the roPosterScreen and then go back up (close) to the grid, everything is fine. When I go from roGridScreen => roPosterScreen => Audio roSpringboardScreen, and then go back up to grid, I get a distorted roGridScreen with a black background at the top and bottom and weird looking album art, etc. - it's almost as if the screen is failing to redraw properly. Has anyone else had this problem? I'm closing everything with Close() on msg.isScreenClosed() and still having issues which i'm guessing is related to stacking order? Any help is greatly appreciated!
Read this thread. You can't stack a roGridScreen like you can other screens. RokuChris mentions video screens, but I've also seen the behavior you're seeing when trying to start audio while a grid screen is open. You can start audio and then display a grid, however (see the SomaFM channel).
Cool. Closing the roGridScreen and reopening each time I return to it is working, though not ideal (have to re-query my API each time, so it takes a few seconds), but it's good to know it'll be fixed later on. Thanks!
"kressaty" wrote: Cool. Closing the roGridScreen and reopening each time I return to it is working, though not ideal (have to re-query my API each time, so it takes a few seconds), but it's good to know it'll be fixed later on. Thanks!
You might consider doing something like I do, and have a wrapper "class" for the grid screen that caches the current screen of data, and opens/closes the screen as appropriate, so you don't have to query your API every time. You can then use it in a stack the same as any other screen, with the exception of needing to call "Hide()" and "Show()" or whatever on your wrapper class.