Reply to thread

Message

<blockquote data-quote="doskabouter" data-source="post: 930002" data-attributes="member: 98267">Had the most odd experience yesterday, I was using the webbrowser plugin while listening to music in the background, and when I pressed navigate back, or forward, the music also skipped to the previous track.&nbsp;What I did was navigate to the music plugin, selected some album, and start play. Next I navigated to the webbrowser and started browsing.I did research it a bit: Set a breakpoint in the webbrowser plugin source on a line that handles the navigate back/forward, and when I press back/forward the breakpoint was caught, but the music already skipped a step.On a second attempt (after visual studio got focus due to the breakpoint) navigation went well for the webbrowser, and didn't interfere with music playing.&nbsp;So it seems that the calling order for OnAction for all GuiWindow (and its descendants) is a bit random.&nbsp;Can anyone explain why it's not always the active window which gets the OnAction first, and is there a possibility to flag that action as handled, so that other windows won't act on it?</blockquote>

[QUOTE="doskabouter, post: 930002, member: 98267"] Had the most odd experience yesterday, I was using the webbrowser plugin while listening to music in the background, and when I pressed navigate back, or forward, the music also skipped to the previous track. What I did was navigate to the music plugin, selected some album, and start play. Next I navigated to the webbrowser and started browsing. I did research it a bit: Set a breakpoint in the webbrowser plugin source on a line that handles the navigate back/forward, and when I press back/forward the breakpoint was caught, but the music already skipped a step. On a second attempt (after visual studio got focus due to the breakpoint) navigation went well for the webbrowser, and didn't interfere with music playing. So it seems that the calling order for OnAction for all GuiWindow (and its descendants) is a bit random. Can anyone explain why it's not always the active window which gets the OnAction first, and is there a possibility to flag that action as handled, so that other windows won't act on it? [/QUOTE]

Verification