| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Co-Authored-By: Narr the Reg <5944268+german77@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
yuzu: Streamline broken Vulkan handling
|
|
|
|
|
|
|
|
|
|
|
|
- These were all somewhat redundant.
|
|
- Avoids new GCC 12 warnings when Type is of form std::optional<T>
- Makes more sense this way, because ranged is not a property which would change over time
|
|
qt_web_browser: Fix button inputs with QtWebEngine
|
|
|
|
Solves MSVC compile error. Also drops need string use for comparison.
|
|
Adds some comments, removes unused includes, and removes last bits of
logging since this is before the logging backend starts up.
|
|
Wow fork() is nice, isn't it?
|
|
|
|
|
|
|
|
settings: Consolidate RangedSetting's with regular ones
|
|
Button inputs were broken as button was assumed to be the bit position of NpadButton prior to the input rewrite. Since this was changed to use NpadButton directly, we should count the number of trailing zeros to determine the bit position.
|
|
tweak API usage in qt_web_browser.cpp
|
|
The latest git version of GCC has issues with my diamond inheritance
shenanigans. Since that's now two compilers that don't like it I thought
it'd be best to just axe all of it and just have the two templates like
before.
This rolls the features of BasicRangedSetting into BasicSetting, and
likewise RangedSetting into Setting. It also renames them from
BasicSetting and Setting to Setting and SwitchableSetting respectively.
Now longer name corresponds to more complex thing.
|
|
|
|
In testing future versions of Qt I forgot to compile with `YUZU_USE_QT_WEB_ENGINE`, so with that flag enabled there are two issues that cropped up.
1. yuzu currently uses setRequestInterceptor, added in Qt 5.6, deprecated in 5.13 with this explaination at https://doc.qt.io/qt-5/qwebengineprofile-obsolete.html
Interceptors installed with this method will call QWebEngineUrlRequestInterceptor::interceptRequest on the I/O thread. Therefore the user has to provide thread-safe interaction with the other user classes. For a duration of this call ui thread is blocked. Use setUrlRequestInterceptor instead.
2. QWebEngineSettings::globalSettings() pointer no longer exists in later versions of Qt
From what I can tell, QtNXWebEngineView doesn't need to set these globally,
when we make changes to settings(), QtWebEngineView::page() creates the page
object if it doesn't exist yet. I don't see the page object being destroyed
or otherwise replaced, except via destroying the QtNXWebEngineView object.
The globalSettings() make sense if Pages or Views objects are being
created outside of yuzu's control.
To test this I've compared what BrowseNX and Odyssey's Action guide do in mainline 1049 and this PR.
For now we're going to go up the chain to QWebEngineProfile::defaultProfile()->settings()
|
|
|
|
yuzu: Make variable shadowing a compile-time error
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
core/debugger: support operation in yuzu-cmd
|
|
log the MSVC runtime version when running on MSVC build
|
|
deprecate usage of QDesktopWidget for going fullscreen
|
|
retranslate the game list placeholder
|
|
general: Set renderer_backend's default to Vulkan
|
|
This might be useful information, not 100% sure.
[ 0.958068] Frontend <Info> yuzu\main.cpp:GMainWindow:275: yuzu Version: yuzu Development Build | master-0b9ef3c0b-dirty
[ 0.958095] Frontend <Info> yuzu\main.cpp:LogRuntimes:220: MSVC Compiler: 1931 Runtime: 14.32.31326.0
|
|
This is the "Double-click to add a new folder to the game list" message
that shows up when users first launch yuzu and is most likely never seen
again. Previously this message was not re-translated.
|
