"mainmanc" wrote:"TheEndless" wrote:"mainmanc" wrote:
I am not having an issue with state, but it certainly is misleading when an error is thrown up on the console. As a programmer, that justs drives me nuts every time I see it . If it is indeed a situation based on the "unexpected" return to the Home screen (which is appears to be) there should be at least some mechanism to either suppress or handle a clean return internally, instead just throwing an error, in my opinion.
My guess would be that it's not actually returning and invalid msg, but instead killing the "wait" itself so msg is never set, in which case, it would be your code's responsibility to handle that situation, not the Roku.
Yeah, that would make sense. What do you recommend as the best approach to handle those situations through code?
EDIT: Actually this looks more like the issue I'm talking about. http://forums.roku.com/viewtopic.php?f=34&t=28472&start=0
Something strange I've come across that I haven't understood...
To learn more about what events come to a port, I've had 'print type(msg)' lines. And a few times when I pressed home, the box would get stuck in an endless loop printing 'invalid'. And part of the time when that would happen, I would get back the the channel list, but I wouldn't be able to get into any channel unless I rebooted roku. Just curious if anyone else has seen that error, and knows the reason.
msg = wait(0, port)