| Age | Commit message (Collapse) | Author |
|
* Improvement in Directory Path Detection for Shortcuts
This pull request updates how the directory path for shortcuts is determined. The main changes are:
1. Replaced the use of environment variables to determine the path of the desktop and applications menu with `QStandardPaths::writableLocation`. This change addresses an issue where the desktop path was not correctly identified when its location was customized, as shown in the attached screenshot.
2. Added conversion from `QString` to `std::string` using `toUtf8()`, which correctly handles non-ASCII characters in directory paths. This change ensures that directory paths containing Portuguese words like "Área de trabalho" are supported.
3. Replaced directory checking using `Common::FS::IsDir()` with `QDir::exists()`.
These changes should improve cross-platform compatibility and code robustness. Because it couldn't locate my desktop, which wasn't on the C drive, but on the F, and even though localization wouldn't work because it was setting it to find the 'Desktop' folder and in the computer's language it says 'Área de trabalho', that will fix for other languages too.
* Update main.cpp
* formatting
* Update src/yuzu/main.cpp
Co-authored-by: Tobias <thm.frey@gmail.com>
* Update src/yuzu/main.cpp
Co-authored-by: Tobias <thm.frey@gmail.com>
* Update main.cpp
* Update main.cpp
* Update main.cpp
desktopPath > desktop_Path
applicationsPath > applications_Path
* Update main.cpp
* formatting
* Update main.cpp
This code will attempt to use QStandardPaths to find the applications directory. If that fails, it will resort to using the ~/.local/share/applications directory, which is a common location for application shortcuts in Linux.
* Update main.cpp
* formatting
---------
Co-authored-by: Tobias <thm.frey@gmail.com>
|
|
- 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
|
|
service: am: Add support for LLE Album Applet
|
|
yuzu: Add desktop shortcut support for Windows (continuation of #11344)
|
|
yuzu-qt: Track play time
|
|
|
|
Allows creating desktop shortcuts with icons for yuzu games.
Co-Authored-By: Jeroen van Schijndel <13182141+roenyroeny@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
qt: add verification for installed contents
|
|
am: Implement UserChannel parameters
|
|
|
|
Used by the Super Mairo 3D All-Stars collection.
|
|
configure_graphics: Fix handling of broken Vulkan
|
|
core: implement basic integrity verification
|
|
|
|
|
|
Otherwise caused a blue Vulkan badge to appear in the status bar.
|
|
|
|
qt: fix romfs dumping for multiprogram applications
|
|
am: shorten shutdown timeout when lock is not held
|
|
|
|
|
|
|
|
|
|
general,config-qt: Present Console Mode as an enum with separate options in game properties
|
|
|
|
from CLI
Fixes updates and DLC not being loaded when launching yuzu from the command line.
Similar to https://github.com/yuzu-emu/yuzu/pull/11357.
Fixes https://github.com/yuzu-emu/yuzu/issues/8352,
|
|
|
|
Old Clang is fussy about this.
|
|
|
|
Allows some special interactions with it in the Qt frontend.
|
|
|
|
The new enum macros don't support setting values directly.
For LastAA and LastFilter, this means we need a simpler approach to loop
around the toggle in the frontend...
|
|
|
|
|
|
The increased buffer size means that that progress bar size has to be adjusted
|
|
|
|
Other programs may change this value, but if thousands of syscalls in this loop is undesirable, then we can just set this once.
|
|
|
|
qt: add option to disable controller applet
|
|
SDL has internally fixed shenanigans related to wakelocking through DBus
from inside sandboxes from around August 2022, so we can now remove the
workaround we used since 2021.
|