johnmarsden
Visitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2017
12:01 PM
Roku dialogs are saving button presses and applying them later...
This used to happen to me with roScreen, but it's also happening to me in Scene Graph.
If I open a Roku modal, especially the purchase dialogs, it records the button presses and then fires them again after you close it. So you'll press "OK" on the dialog to close it, but it then fires that same OK event and the message system picks it up. So then I get caught in an indefinite loop.
I've implemented a system where I ignore the next automatically delivered click event when Roku dialogs are used, but this is the hackiest thing ever. I'm really hoping this is adjustable in some way. I have a regular running loop that catches all events and basically triggers a broadcast for certain things, like "OK" press, and then pages will have an event handler. When the modals are open.. the button presses are seemingly saved up and executed once the dialog is closed. That seems like a Roku bug to me. Why would the events be handled by the dialog AND sent to the loop AFTER the dialog closure? It's essentially doubling their effect.
Tips? Thoughts?
If I open a Roku modal, especially the purchase dialogs, it records the button presses and then fires them again after you close it. So you'll press "OK" on the dialog to close it, but it then fires that same OK event and the message system picks it up. So then I get caught in an indefinite loop.
I've implemented a system where I ignore the next automatically delivered click event when Roku dialogs are used, but this is the hackiest thing ever. I'm really hoping this is adjustable in some way. I have a regular running loop that catches all events and basically triggers a broadcast for certain things, like "OK" press, and then pages will have an event handler. When the modals are open.. the button presses are seemingly saved up and executed once the dialog is closed. That seems like a Roku bug to me. Why would the events be handled by the dialog AND sent to the loop AFTER the dialog closure? It's essentially doubling their effect.
Tips? Thoughts?
4 REPLIES 4
johnmarsden
Visitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2017
10:49 AM
Re: Roku dialogs are saving button presses and applying them later...
Bump.
NB_
Roku Guru
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2017
03:37 PM
Re: Roku dialogs are saving button presses and applying them later...
Can you provide a MWE (minimal working example) to repro?
please
please
destruk
Streaming Star
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2017
09:42 PM
Re: Roku dialogs are saving button presses and applying them later...
In this case, wouldn't a MBE (minimal buggy example) be more useful? 🙂

squirreltown
Roku Guru
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2017
12:44 PM
Re: Roku dialogs are saving button presses and applying them later...
"destruk" wrote:
In this case, wouldn't a MBE (minimal buggy example) be more useful? 🙂

Kinetics Screensavers