screensaver implementation is non-trivial so I don't understand why there's no documentation on it.
The app channel I'm trying to write displays a blank screen on screen saver mode.
Just add a RunScreensaver() function to your code, and it will get executed when the screensaver kicks in. Is your channel using the 2D API, by any chance? If so, that would be the problem. The screensaver won't run over a 2D screen ...
So, the system-wide screen saver (henceforth "global SS") is used for channels w/o RunScreensaver() and outside of channels? If i add RunScreensaver() to my channel, that will be ran instead of the global SS? Unless i have a roScreen alive, then none of the two SS will be called - instead screen will be blackened. Adding an appropriate flag to the manifest will make my SS selectable as system-wide SS? What's the timeout to activate the local SS, is that the global value from Settings?
Oh, frak me!
It's been almost 4 years since screen savers were introduced and they still haven't had time to document it?
- Entered when the Roku has hit the configured idle-time. The screensaver to launch is selected by the user on the Screensaver settings page.
- The Roku box may not start the custom screensaver and will use a default screensaver instead if there is insufficient memory to start a screensaver slideshow
- roVideoPlayer and roAudioPlayer are not allowed to be run in a screensaver
- If you have any dialogs with ShowBusyAnimation() enabled, you’ll want to make sure you close and kill the reference before painting a new screen on top of them. Otherwise, your app may lose focus when returning from the screensaver.
- Entered when the user selects “custom settings” on the Screensaver settings page and the application is configured as the system screensaver.
Pretty sure it's
*This is just embarrassing. Like people who bondo their dents but never paint them. So close to finishing the job and then....Squirrel!
"RokuJoel" wrote:Thank you for shedding light on how things work. I thought it was a good thing when RokuPatrick opened the Dev.blog with introducing the team at the time. Surprising there are only a few devs on the "using Roku" side, considering company is hundreds of people. If there is too much (over)work, mgmt might consider adding extra help.
Developer Support Manager, we do have at least three people with the same title, that would be, in org chart order top down:
Rob and Kevin are the Docs folks, however their primary role is developer support of channels like Hulu+, Fox, Amazon etc.
Chris does a lot of in-house development for those partners.
My role is as the developer support lead for the rest of our development community, plus I occasionally am tasked with creating screensavers and holiday channels. I'm not directly involved with documentation writing other than to forward documentation issues that developers turn up on the forums to Rob & Kevin. Myself and Danny Ng are responsible for processing and publishing all your channels as well as developer support. But not Docs. Rob has initiated a project in which I am involved to reorganize and update all the docs.RokuRobB and RokuKevin should be so kind to come to the forum and address the documentation issues brought here. Like this screen saver doco that has been missing for at least a year (trusting TheEndless, it is somewhere in the old PDFs). It is a gaffe when something like that - repeatedly asked since - has not been noticed and fixed. Some of my questions below are also doc ones. I get the gut feeling they are saying "this is under my level, talking to the plebs".
The relationship between Roku and "Squirreltown" is that he signed the developer agreement, has published a channel, and posts on our forums.Oh, that was a joke to something Squirreltown said - if you see the thread above - namely "*This is just embarrassing. Like people who bondo their dents but never paint them. So close to finishing the job and then....Squirrel!" - was wondering if nickname relates.
Which more difficult technical issues do you feel haven't been answered? Let me know and I'll attempt to answer them or find someone who can. In some cases the answer may be "we are not going to answer that question at this time" as some things may be in regard to trade secrets or product releases that may be in the works.I thought about that and sure - it is understandable some responses might be "answer denied, we consider this proprietary information/trade secret - at this time". Or "we consider it unimportant to fix" or "can you explain to me the significance of this?".
I was drawn here by your hilariously titled `objfun = no fun`.
Are you on the slack group? It's got about 60 people and a some of roku's engineers roku regularly chime in.