mangoapp: plumb engineName #1653
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Dec 5, 2024
pac85
force-pushed
the
plumb_engine_master
branch
from
24d72ca to
edecd7a
Compare
pac85
force-pushed
the
plumb_engine_master
branch
from
edecd7a to
055c6b0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR modifies gamescope to use the swapchain feedback internal extension to send the
engineNamefield ofVkApplicationInfoto gamescope which will in turn send it to mangoapp for displaying it.I'm not entirely sure on whether the
focusWindow_engineglobal would require some locking, I assumed it wouldn't since the pid in the previous implementation of this feature is read and written without any locks.Mangohud side: flightlessmango/MangoHud#1498