Skip to content

Conversation

@mikeller
Copy link
Member

@mikeller mikeller commented May 3, 2020

Supersedes #1990.

@asizon: Turns out this one is a bit more complex: The problem warning just pops a dialog, but then proceeds to finish the connection, which also removes the timer. In the case of the 'Reset to defaults' dialog we don't want to finish the connection, as the most likely outcome is that the user will want to reset, so we need to remove the timer, and then restart it in the case that the user cancels and we complete the connection.

@mikeller mikeller added this to the 10.7.0 milestone May 3, 2020
@asizon
Copy link
Member

asizon commented May 3, 2020

Thanks for looking into it!!Now I can see everything even clearer, with this code we manage to respect 100% of the current init timeout. We can also call the timeout when we want just using your new function setConnectionTimeout, nice!

@mikeller mikeller merged commit 39c2d63 into betaflight:master May 4, 2020
@mikeller mikeller deleted the fix_reset_dialog_timeout branch May 4, 2020 12:36
@mikeller
Copy link
Member Author

mikeller commented May 4, 2020

Wohooo, that was #2000 by the way, good work everybody, keep them coming!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants