| Age | Commit message (Collapse) | Author |
|---|
|
Replaces every way of handling config for each frontend with SimpleIni. frontend_common's Config class is at the center where it saves and loads all of the cross-platform settings and provides a set of pure virtual functions for platform specific settings.
As a result of making config handling platform specific, several parts had to be moved to each platform's own config class or to other parts. Default keys were put in platform specific config classes and translatable strings for Qt were moved to shared_translation. Default hotkeys, default_theme, window geometry, and qt metatypes were moved to uisettings. Additionally, to reduce dependence on Qt, QStrings were converted to std::strings where applicable.
|
|
core: hid: Split SL and SR buttons
|
|
|
|
|
|
|
|
- Show the right confirm dialog if wanted
- Create generic method to ask close confirmation
- Add "R + Plus + Minus" default shortcut to Restart emulation
|
|
- Add General setting to choose if a confirm dialog is shown when stopping
- Show the right confirm dialog if wanted
- Reuse dialog window that ask to close the game
- Add "L + Plus + Minus" default shortcut to Stop emulation
- Create generic question dialog based on TAS dialog
- It allows controller interaction on most dialogs
|
|
Allows some special interactions with it in the Qt frontend.
|
|
|
|
Turns out the network interface is in the Services category. Can't wait
get rid of this whole config.
Addresses yuzu-emu/yuzu/issues/11205
|
|
ReadSetting with the default is a convenience function reading
settings, not for use in an internal environment. It tries to manage
the default value of a setting.
|
|
|
|
Previously was not respecting whether the setting was default.
|
|
|
|
|
|
Almost a 2 year old migration setting now
|
|
Reduces compile times a tad on clang.
|
|
|
|
|
|
|
|
Me shooting myself in the foot 3 days in advance.
|
|
We were passing so many objects between the function and the caller that
it needed to be redesigned.
|
|
Will help with generating config UI later.
|
|
LoadString: Sanitize input
settings: Handle empty string, remove redundant category
settings: Rename Input to Controls, FS to DataStorage
settings: Fix Controls groups information
settings: Move use_docked_mode to System (again)
settings: Document
settings: Add type identification function
settings: Move registry into values
settings: Move global_reset_registry into values
settings: Separate AdvGraphics from Renderer
settings: More document
squash
settings: Use linkage object
uisettings: Move registry into settings
Probably wont build without
uisettings: Use settings linkage object
config: Load settings with a map
Uses the new all_settings vector to load settings.
qt-config: Rename settings category
qt config: Rename to read category
config: Read/write contols category with for_each
This is extremely limited due to the complexity of the Controls group,
but this handles the the settings that use the interface.
qt-config: Use new settings registry
qt-config: Read/write advgrphics
qt-config: Use settings linkage object
yuzu_cmd: Load setting off of vector
cmd-config: Finish settings rename
config: Read controls settings group with for_each
cmd/config: Move registry into values
cmd: Read adv graphics
cmd-config: Use settings linkage object
|
|
Just puts them all neatly into one place.
|
|
|
|
qt: add option to disable controller applet
|
|
input_common: Redesign mouse panning
|
|
|
|
|
|
qt: persist framerate sync option
|
|
|
|
|
|
add context menu for status bar settings
|
|
|
|
|
|
configure_graphics: Add option to enable compute pipelines for Intel proprietary
|
|
|
|
|
|
This option is only visible if an Intel GPU using the proprietary
driver is found during Vulkan device enumeration.
configure_graphics: More directly get driver id
Vulkan::Device does quite a bit more than we need just to see the
driver ID here.
|
|
configuration: Expose separate swap present modes
|
|
|
|
settings: rename extended memory layout to unsafe, move from general to system
|
|
Previously, yuzu would try and guess which vsync mode to use given
different scenarios, but apparently we didn't always get it right. This
exposes the separate modes in a drop-down the user can select.
If a mode isn't available in Vulkan, it defaults to FIFO.
|
|
|
|
|
|
|
|
texture_cache: Add asynchronous ASTC texture decoding
|
|
|
|
|
