Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Prevent duplicated callSurfaceChanged call when exiting immersive mode #2961

Merged
merged 1 commit into from
Mar 13, 2020

Conversation

MortimerGoro
Copy link
Contributor

Fixes #2957

Comment on lines 316 to +317
mSession.setActive(true);
if (!SettingsStore.getInstance(getContext()).getLayersEnabled()) {
if (!SettingsStore.getInstance(getContext()).getLayersEnabled() && !mSession.hasDisplay()) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we can just check if the mSession is active and then only call setActive(true) and callSurfaceChanged() if it isn't?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think is safer to keep this check. My worry is that other place of code calls SetActive before this method and in that case we would miss the surfaceChanged call

@bluemarvin bluemarvin merged commit 441566d into master Mar 13, 2020
@bluemarvin bluemarvin deleted the v10/pico_exit_vr branch March 13, 2020 17:10
@MortimerGoro MortimerGoro self-assigned this Mar 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Pico] The open windows ca no longer be scrolled after exiting immersive mode
2 participants