summaryrefslogtreecommitdiff
path: root/Source/Core/VideoCommon/ShaderCache.cpp
diff options
context:
space:
mode:
authorPokechu22 <Pokechu022@gmail.com>2023-04-17 23:18:42 -0700
committerPokechu22 <Pokechu022@gmail.com>2023-04-17 23:23:36 -0700
commit801fa8e905c9ff73c993c940e3e7966e55efc4cb (patch)
treecbf409a47bb9951e26580a6d7bf25f6aa6bc24b7 /Source/Core/VideoCommon/ShaderCache.cpp
parentc0b6e9e69cd7a0f5519824b5f24ec232d43590a7 (diff)
Only force-show the code widget when first enabling the debugger
Before, any call of Settings::SetDebugModeEnabled(true) would show it. This means that if the debugging UI is enabled, but the user manually closed the code widget, then toggling any option on the interface pane (such as "Pause on Focus Loss") would cause the code widget to reappear. Additionally, closing and reopening dolphin did not call SetDebugModeEnabled, so the code widget did not reappear in that case (it only appeared after touching the interface pane). This is a bit silly, so now only enabling the debugger does it. This also somewhat resolves an inconsistency introduced by the previous commit: prior to it, --debugger would call SetDebugModeEnabled(true) and thus show the code pane; after these commits, it does not, as it acts like a config change. This is a behavior difference, but not a particularly important one.
Diffstat (limited to 'Source/Core/VideoCommon/ShaderCache.cpp')
0 files changed, 0 insertions, 0 deletions