Thanks for clearing that up. Perhaps you know something about the new ROKU app. The last time I checked (it has been a couple of months, perhaps something changed ), holding down any of the scroll icons resulted in an extra set of key press being sent to the device when the icon was released. ( At least this occurs in my own channel ); however, This does not occur with a single key down/up only when holding down the icon for continuous scroll. This behavior was not present in the old app and is not consistent with the way the remote works. I have verified the extra sequence in my own code. As there really is no way to tell what device is sending commands it cannot be intercepted and ignored
I was referring to how the remote itself behaves. The events delivered to Brightscript use a different paradigm. If you look at the remote through a cellphone camera, you will see that while you hold a button down, the remote is sending continuous codes. (Well not actually continuous; it repeatedly sends 180 ms codes with a 30 ms gap between codes.) When you release the button it stops sending. The firmware sends one press event to Brightscript when it receives the first code, and synthesizes a release event when it fails to get another code in the expected time.
Huh, that's an interesting one. It could be either because of change of what "Roku by Roku" app ECP-sends has changed - or it might be a change in the firmware too. How does my "old faithful" remote app (https://itunes.apple.com/us/app/remote- ... d438407178) behave with your channel? That is if you are about iOS. If both apps (mis)behave the same, we blame it on the firmware (or your channel 🙂 ). If they differ - it may be the app.
@BradC, does it have to be in B/S app?
I was just able to get it to happen on the main roku screen. Yaaaaay.
it's scrolling indefinitely now, as I type (with both hands obviously) and my remote is lying beside me with no buttons pressed.
... watching those icons go by is enough to make me happy I'm not insane.