(FB21294645) In Xcode 26.2 RC, pinning a pushed window to a wall breaks pushWindow for all other apps on the system
| Bluesky | https://bsky.app/profile/drewolbrich.bsky.social |
Drew Olbrich
@drewolbrich
- 240 Followers
- 252 Following
- 551 Posts
I'm creating an app that explains the theory of special relativity using interactive 3D spacetime models, for Apple Vision Pro, iPhone and iPad
(FB21287011) In visionOS 26.2 RC (23N301), when a window presented with pushWindow is dismissed, its parent window reappears in the wrong location
In the RealityKit app I'm developing, I'm using ModelDebugOptionsComponent.VisualizationMode for debugging, but I also wanted to display other information that ModelDebugOptionsComponent does not support, like ModelSortGroupComponent draw order.
I created a hacky ECS scheme to swap in and out my own custom debug materials before and after each frame is rendered.
On iPadOS 26 beta, the navigation bar can appear inset underneath the status bar (FB18241928)
FB17567515 - RealityKit Scene class documentation web page is inaccessible
TL;DR: https://developer.apple.com/documentation/realitykit/scene previously described the RealityKit.Scene class and now describes the USD ChangeSceneAction.scene property.
Xcode inserts unwanted apostrophes into Markdown and XML files.
Every time you type a word like "don't", a second apostrophe is inserted after the word and you have to delete it.
Repro steps:
1. Create a new empty Markdown file.
2. Open the file in Xcode.
3. Type the word “don’t”.
Expected behavior: The word “don’t” appears.
Observed behavior: The word “don’t” appears, followed by an extra single quote.
IMO, physicists who are proponents of the block universe model of spacetime should put their money where their mouth is and submit a patch that would make this possible:
git bisect start
git bisect bad HEAD
# Mark the commit 100 commits *after* HEAD as "good"
git bisect good HEAD~-100
It's lame that you can only run `git bisect` against past commits.
An extension of `git bisect` that accepted future commits as arguments would be helpful to me right now, to track down exactly when and how I'll finally implement that feature I've been dreading.