So to enable and disable the effect, in my case, I need to track which header is pinned to the top, and call _setActive: on the interactions of the header views to only enable for the top one. I extended UICollectionViewLayoutAttributes with a fields for this.
And it works.
October 13, 2025 at 3:28 PM
So to enable and disable the effect, in my case, I need to track which header is pinned to the top, and call _setActive: on the interactions of the header views to only enable for the top one. I extended UICollectionViewLayoutAttributes with a fields for this.
If you create an _UIScrollPocketContainerInteraction instance and add it to the view, it actually works. But it creates an amusing effect where all glass effects are synchronized.
October 13, 2025 at 3:27 PM
If you create an _UIScrollPocketContainerInteraction instance and add it to the view, it actually works. But it creates an amusing effect where all glass effects are synchronized.
An Apple UICollectionViewLayout subclass vs a custom one. Notice the header visual effect view's glass is "synchronized" with the navigation bar, making them switch appearance together. No way there is a UIGlassContainerEffect in there somewhere.
October 13, 2025 at 3:23 PM
An Apple UICollectionViewLayout subclass vs a custom one. Notice the header visual effect view's glass is "synchronized" with the navigation bar, making them switch appearance together. No way there is a UIGlassContainerEffect in there somewhere.
Photos on iOS 26 does not use the public bottomAccessory/UITabAccessory API, yet is able to detect when the tab bar minimizes and make that bar fade in and out. Inspecting the hierarchy shows it's just a UIView subclass. So how does it know when the tab bar minimizes?
September 26, 2025 at 12:55 AM
Photos on iOS 26 does not use the public bottomAccessory/UITabAccessory API, yet is able to detect when the tab bar minimizes and make that bar fade in and out. Inspecting the hierarchy shows it's just a UIView subclass. So how does it know when the tab bar minimizes?
Xcode is a buggy, retarded mess. Pause once, and you get disassembly for each stack frame. Pause a second time, and Xcode is broken. It's not lldb, as `disassemble` produces the correct output. How is that team so incompetent? Then again, what isn't at Apple these days?
April 13, 2025 at 12:46 PM
Xcode is a buggy, retarded mess. Pause once, and you get disassembly for each stack frame. Pause a second time, and Xcode is broken. It's not lldb, as `disassemble` produces the correct output. How is that team so incompetent? Then again, what isn't at Apple these days?