Forum Discussion

JohnBasedow's avatar
11 years ago

Bug?: roSearchScreen and roSearchScreenEvent::isButtonInfo()

The API docs say this about the roSearchScreenEvent's isButtonInfo() function:
http://sdkdocs.roku.com/display/sdkdoc/ ... creenEvent
The Info remote key was pressed. This is only emitted for the search results on the right side of the screen.


Except if you have one of the buttons on the lower part of the screen focused, and hit the info button, the isButtonInfo() event gets fired, and the msg.GetIndex() returns 0.

Because of this, and the lack of a way to tell if the search results list is focused, there is no way to tell if the combination of the isButtonInfo event and msg.GetIndex() == 0 is actually occurring over the search results list.

If msg.GetIndex() returned an invalid value, or a special value based on the button selected, that would be more useful, but as it stands, this will cause unwanted side effects for channels using the info button on the search screen.

3 Replies

  • Sounds like implementation bug, doesn't it?
    Since documentation states "*" should "only emit[] for the search results" - and logically that's what makes sense too.
  • "EnTerr" wrote:
    Sounds like implementation bug, doesn't it?
    Since documentation states "*" should "only emit[] for the search results" - and logically that's what makes sense too.



    You mean the Roku firmware implementation, and not mine, right?
  • "JohnBasedow" wrote:
    You mean the Roku firmware implementation, and not mine, right?

    Yes, that firmware does not act as it should've.