summaryrefslogtreecommitdiff
path: root/rs/java/android/renderscript/ProgramFragmentFixedFunction.java
diff options
context:
space:
mode:
authorWinson Chung <winsonc@google.com>2020-05-26 21:16:48 -0700
committerWinson Chung <winsonc@google.com>2020-05-26 21:28:32 -0700
commitd34b4e8d278386b85a00018c502bd21d00f8813b (patch)
tree890e1c252d715c58674bb854ce6e3a47230b8de3 /rs/java/android/renderscript/ProgramFragmentFixedFunction.java
parent125bdd8ca1653ab9eb44e845629a5fdade3bcb56 (diff)
Fix inconsistency in nav mode changes
- Don't rely on the broadcast for determining overlay changes, the actual changes are propagated via asset path changes to the configuration only after which the correct resources can be read - Remove unnecessary reloading of nav bar when changing modes, basically in the rare cases that the configuration change comes before the receiver what happens is that NavBarFragment is reloaded (because FragmentHostManager detects an interesting config change), but the NavigationModeController has the old value (because it hasn't received the broadcast), then when it receives the broadcast, it has to reinflate with the new mode. Now that NavModeController is based on config changes (and FragmentService always posts config change updates) the NavModeController mode will always be updated before the fragment is reloaded (and NavBarInflaterView doesn't need to update on mode change at all) - Remove some dead code Bug: 156631944 Test: Change nav modes a bunch of times Change-Id: I14ba57acab3683fcd187d0d4adcf87dc7e352b1d Signed-off-by: Winson Chung <winsonc@google.com>
Diffstat (limited to 'rs/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions