Phillip Caudell @phill@mastodon.notsobig.co

Ooo DocC now includes extensions in Xcode 15!

👏 👏 👏

Why is deinit not called here?

If a StateObject's lifetime is that of the containing view, popping from the stack should deallocate it. But it doesn't.

Weirdly removing the List's selection binding results in a dealloc as expected.

Is this a memory leak with List or am I missing something? (iOS 17/latest Xcode)

https://gist.github.com/phillipcaudell/8509aba4f3fc064b3d7bfbb1fefbe9a9

“Your engineers were so preoccupied with type-safety that they didn't stop to think if they should”

– Ian Malcolm, 1993

I need an ”AnyCodable" type for serialising some generic stuff.

Is something like this the best approach now that we have existentials on protocols?

AnyThoughts appreciated!

https://gist.github.com/phillipcaudell/99d1fe52873d0c5115bc281272003784

The only brushed metal I’m interested in

I'm a little embarrassed to admit, but I had been blissfully unaware that View extensions are type erasing.

That means if you have an extension for using your ViewModifier in a more ergonomic way, it'll be erased to AnyView unless you explicitly mark it as @inlinable.

https://gist.github.com/phillipcaudell/df04ebf01e9579a308e3534ac829a540

Edit: Perhaps this is just a quirk of Xcode Previews: https://mastodon.notsobig.co/@phill/111051676536041177

If you're wondering why Big Mail is taking so long

NavigationStack loses its navigation bar on iPad when returning from the background, making it impossible to go back or do anything. iOS 16 and 17.

FB13120953

https://gist.github.com/phillipcaudell/f6258c1fbac69a9fb2cd030fadd087de

Something that tripped me up recently was not understanding how .onAppear { } behaves on iPad.

It gets called multiple times, even though the view is not visible.

Why? Logging reveals the size class is also changing, so presumably iOS is taking snapshots for the app switcher.

If like me you rely onAppear to denote a user has seen something (say, Mark as Read), you'll need to check the scenePhase first.

Here's a gist: https://gist.github.com/phillipcaudell/290eab2c42c4cc27cfdc0c595b40654d

i am inevitable.

Here’s one weird #SwiftUI trick Apple DON'T want you to know:

If you present a confirmation dialogue from a swipeAction or contextMenu nothing will happen as the view is removed before the dialogue is presented. Annoying, but it makes sense.

Instead, delegate the confirmation to the environment. Now the Button isn't responsible for the presentation and you're left with a nice clean call site.

Here's my implementation with an example: https://gist.github.com/phillipcaudell/ecb32dc5a3915931d225a6cb8a67ac34

List on Mac

the REAL cost of the gay agenda

i’m pleased to report you can make the iPhone simulator gay now

Man, NavigationSplitView is *still* broken in iOS 17 beta 7.

I reported back in May (FB12178616) that when in compact mode transitions become sporadic and stop working. This code is verbatim from Apple’s docs and it doesn't work.

This broke back in iOS 16.2. It seems nuts to me something so significant can stay broken for this long (and on a relatively new API?!)

https://gist.github.com/phillipcaudell/4cc223bec9a18970aed489d06580a56d

I recently got downvoted into oblivion for explaining why someone's List animation was glitching, perhaps because the solution is so simple it seems stupid.

On the left is swipeAction with a Button. On the right is the exact same Button, but now the animation is smooth.

The difference? I set the Button's role to destructive. SwiftUI uses the role to infer what animation to use. https://gist.github.com/phillipcaudell/e4ee5057dc33f92ed80b817762726275

live scenes of me keeping all size classes and platforms working from a single target

what did you call me

As of beta 6 it seems to be reporting the wrong value if more than one row is selected on iPad.

I've filed a feedback for any Apple folk who see this 👉 FB13014204

Happy to see iOS 17 now gives our views a way to respond to the List selection style.

By reading the backgroundProminence value in the environment our custom controls, say an unread indicator, can adjust their tint as not to be occluded by the background: https://gist.github.com/phillipcaudell/e2ca686fcd6744b8341ac54f240a7798