-
-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a get_info method to get GL_VENDOR, GL_RENDERER, GL_VERSION #375
Open
uggla
wants to merge
10
commits into
not-fl3:master
Choose a base branch
from
uggla:gl_info
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Library shouldn't print anything when things are working correctly.
native/linux_x1: fix set_fullscreen Changed XEvent and XPropertyChange when fullscreen var is false.
native/wasm: implement window_minimized_event - added extern fn focus in wasm.rs - added a call to this fn in gl.js - added calls from XEvent 9 and 10 to the window_events
native/linux_x11: implement set_window_sze
This approach is valuable when working with native applications to determine the renderer in use. It proves particularly beneficial when dealing with the Nvidia Optimus renderer.
How would this be implemented if we decided to add Metal support? |
I do not have a really strong opinion here, but I feel that this code belongs to a crate/code snippet for a user code. It would be hard to rebase it on 0.4.0 branch (the one with metal), but as a crate it is OK to have it GL/certain OSes only. |
not-fl3
force-pushed
the
master
branch
2 times, most recently
from
May 31, 2023 16:47
e50ada7
to
c9bff8f
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.
My laptop is equipped with Nvidia Optimus technology, but I wasn't sure about the renderer being utilized by my macroquad applications. To address this, this pull request introduces a method to retrieve information such as GL_VENDOR, GL_RENDERER, and GL_VERSION. This method allows for the identification and confirmation of the correct GPU being utilized.
By incorporating this code into the application, it will provide the following output based on the renderer being used: