bugfix(android): Allow Volume*
keys to be passed to the user
#3636
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems that discussions around #2748 (cc @Hoodad) being a poor workaround that should rather be implemented properly/differently drowned out the fact that the workaround was implemented incorrectly to begin with. By having the
if
inside the match arm, rather than /on/ the match arm thekeycode =>
path is /never/ used forVolume*
keys and this event is thus never passed on to the user, defeating the purpose of callinghandle_volume_keys()
. Only theHandled
/Unhandled
state is affected by theignore_volume_keys
workaround, as set byEventLoopBuilderExtAndroid::handle_volume_keys()
.Fix this by moving the
if
workaround on the match arm, so that disabling it viaEventLoopBuilderExtAndroid::handle_volume_keys()
causesVolume*
events to be delivered to user code once again.changelog
module if knowledge of this change could be valuable to users