roSearchScreen enhancement request

Yeah, that makes sense. I think we are/were thinking the same thing, but my idea around the navigation is slightly weird/suboptimal now that I think of it. I was thinking that they user would be able to play/inspect the video from the search screen. When you really think about it, you're doing the same thing twice if you show the suggestions...and then show them again on another screen. But it's probably more intuitive to do it that way; not to mention it would conform to the way netflix works. It would still be nice to have those things I asked for. I think what you do after the "search" is almost inconsequential; I'd still want to search (and get results) just once without creating two sets of arrays. I'd also like to know the exact item I selected. For instance, another reason this is important is because of the lack/inconsistent support of unicode. The suggestions list supports some unicode characters when parsed from XML; but GetMessage() returns ASCII -- thereby eliminating the ability to figure out what the user selected or event re-query with their selection. For instance, test with something like "360°". The suggestions list will display that exact term; GetMessage returns "360?". It would be frustrating to display all matching values, and be on the wrong index.