-
Notifications
You must be signed in to change notification settings - Fork 1.3k
UIKit: detect GL and Metal backing layers #4621
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
Closed
brianconnoly
wants to merge
3
commits into
rust-windowing:master
from
brianconnoly:vss/uikit-layer-backed-detection-master
+4
−2
Closed
Changes from 2 commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I must be missing something, but ... isn't this new code doing the same as the old code? (except that it introduces the use of
unsafe)Edit: nevermind, I see now that it performs the check on the layer, not the view.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of this unsafe, block, would it be possible to use https://docs.rs/objc2-ui-kit/latest/objc2_ui_kit/struct.UIView.html#method.layerClass to obtain the class and then perform the check?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good suggestion to avoid the handwritten unsafe block. A direct
UIView::layerClasscall would inspect the baseUIViewclass, while subclasses may override it, so it is not equivalent to checking the actual backing-layer instance. I enabled theobjc2-quartz-corebindings and now use the safe typedview.layer()result followed byisKindOfClasschecks. This removes the raw pointer and the entire unsafe block.Verification:
cargo check -p winit-uikit --target aarch64-apple-iospasses on macOS. I also tested the same typed access pattern through our 0.30 patch lineage on a physical iPad: signed install and launch passed, rendering looked correct, and the app remained alive through a controlled suspend/resume.