Roku Developer Program

[merthin]

Hi All. I have been playing with an interesting issue as of lately:

I'm working with roScreens and it seems that after 10 minutes of inactivity the usage of wait(timeout, port) takes
longer than what stated in timeout. Rendering the app unresponsive. This port is attached to a roUrlTransfer object.

I wonder if this is an issue some others have found, and if someone from the staff could elaborate in what happens
under the hood (GC, etc) when the blank screen (the screensaver mode for roScreen based apps) appears.

Also, does "wait(0, port)" is the same as doing port.GetMessage()?

thank you all in advance.

[NewManLiving]

I find It's better to use getmessage
Your transfer calls should generally be asynchronous
On their own port. And if absolutely necessary write your
Own screensaver

[TheEndless]

You didn't mention what model you're testing on. There's a known issue with sleeps/waits under 10 ms on the previous gen Roku 2 XD and XS, that probably carried over to the streaming stick as well.

"merthin" wrote:
Also, does "wait(0, port)" is the same as doing port.GetMessage()?

No. Wait(0, port) will block until it receives a message.

[merthin]

Thanks all for the responses. I get around it by making all the call asyncronous.

@TheEndless I was testing in several Rokus, including the 3.