summaryrefslogtreecommitdiff
path: root/Source/Core/VideoBackends/Vulkan/ObjectCache.cpp
diff options
context:
space:
mode:
authorPokechu22 <Pokechu022@gmail.com>2023-04-17 23:11:26 -0700
committerPokechu22 <Pokechu022@gmail.com>2023-04-17 23:11:26 -0700
commitc0b6e9e69cd7a0f5519824b5f24ec232d43590a7 (patch)
tree1a22765a8a3d4a5a5269bd6bb69dd82d19679fcb /Source/Core/VideoBackends/Vulkan/ObjectCache.cpp
parent1a2dcc53f2d7a85b0d49e9d2b12d819a2f57b835 (diff)
Treat --debugger command line as a temporary setting
Before, Settings::SetDebugModeEnabled was used; this calls SetBaseOrCurrent() which will usually permanently change the base configuration setting for the debugger to true. Thus, the debugger would remain active even if the --debugger command line option was removed. Now, it remains active only for the current run, like other command-line options. Note that SetBaseOrCurrent is also used by the "Show Debugging UI" option under Options -> Interface; this means that if the debugger is turned off (or off and then back on) by the user while --debugger is specified, this will be reset to whatever the base configuration had when Dolphin is closed and reopened. This behavior is consistent with the rest of the UI. To my understanding, the --debugger option is something from 5.0 stable/DolphinWx where there was no way to toggle the debug UI in the settings (and the command-line option was the only way of enabling it). It's less useful nowadays.
Diffstat (limited to 'Source/Core/VideoBackends/Vulkan/ObjectCache.cpp')
0 files changed, 0 insertions, 0 deletions