summaryrefslogtreecommitdiff
path: root/src/input_common/drivers/virtual_amiibo.cpp
diff options
context:
space:
mode:
authorGravatar Charles Lombardo2023-03-23 03:46:04 -0400
committerGravatar bunnei2023-06-03 00:05:47 -0700
commit295ffd4d478e93cc1e0c4937403e47e44298beda (patch)
tree0c5175e5c26229e4d8297c78336fa27b1d9e9443 /src/input_common/drivers/virtual_amiibo.cpp
parentandroid: Store settings object in viewmodel (diff)
downloadyuzu-295ffd4d478e93cc1e0c4937403e47e44298beda.tar.gz
yuzu-295ffd4d478e93cc1e0c4937403e47e44298beda.tar.xz
yuzu-295ffd4d478e93cc1e0c4937403e47e44298beda.zip
android: Persist settings across configuration changes
Mostly things get refactored here to remove previous assumptions made about how the activity/fragment lifecycles would operate. The important change for persistence is removing the assumption that the user will be at the first settings fragment on recreation when deciding whether or not to reload settings. Now we check a flag in Settings to know if we loaded the settings within this lifecycle.
Diffstat (limited to 'src/input_common/drivers/virtual_amiibo.cpp')
0 files changed, 0 insertions, 0 deletions