"RokuJoel" wrote:
That seems somewhat strange - which screensaver are you running that "jerks"? This sounds like a cpu usage issue clearly, either by the screensaver or by your app, but I wonder what is going on under the hood of your channel besides waiting and an occasional http request? When you say "waits" is that a sleep(10000000) or is that
while timer.gettotalseconds() < 10000000
end while
or is it
msg=wait(100000000, port)
Basically, unless your channel is duplicating screensaver functionality in some way - the screen is updated frequently, every pixel on the screen is changed at least once every 15 minutes - we want the screensaver to run, we don't want you burning in an image on someones old Plasma flatscreen.
- Joel
- Joel
It is:
msg = wait(1000, msgDialog.GetMessagePort())
and it loops for 300 seconds.
And yes there is some other functionality other than HTTP request. After 300 seconds roMessageDialog closes and a roScreen is shown with a full screen image (basically to show that application is trying to connect to server again and roScreen object is created at this moment and displayed). It is a one time image draw and screen is not drawn again until the HTTP request finishes. And if it is not the time to play videos then screen is closed again but if it is time to play videos then screen refreshes with a new image along with roVideoPlayer to play content.
