#iOSDev issue update: I made a minimal example. As far as I can tell, when you animate passing different images to an Image view, #SwiftUI on iOS 17 animates the size/shape of the new image for some reason. With .resizable() and .aspectRatio(contentMode:) modifiers (the intended way to fit images in a frame according to the documentation), this causes it to stretch bizarrely (without those modifiers, it slides around instead!)
Here's the same code running on iOS 16 (left) and 17 (right)
I implemented a variable blur similar to the effect Apple uses throughout iOS as a metal shader and gave it a #SwiftUI wrapper that lets you control the effect with a mask to create all sorts of effects
On GitHub as a #Swift package: https://github.com/daprice/Variablur – I'll give it a better readme sometime, but for now you can use Xcode's documentation viewer and previews.
Thanks to @twostraws's Inferno project and tutorial for inspiring me to try this!
Welp, this is nasty: when focus leaves a TextField, every scroll view with a scrollPosition modifier anywhere in the app starts behaving unpredictably…
but only on certain devices. I can reliably reproduce it on my iPhone and Mac (“designed for iPad" target) but NOT an actual iPad and not any simulators.
Anyone else have issues animating between images scaled to fill or fit in #SwiftUI after iOS 17? This did a nice crossfade in iOS 16, now it does this weird stretch effect as if it's trying to animate both images to/from the size of the other image.
(it's not just images, I'm seeing a lot of views stretch/squash during animations, even in Apple apps and system UI)
Today I tried again with the exact same #Xcode simulator installation command that was giving me "disk almost full” errors for the past few days, and it Just Worked™.
I literally did nothing, just closed my laptop yesterday, opened it today, and the problem is magically gone. I have the exact same amount of disk space that wasn't enough yesterday.
Really sucks having to wait an unspecified number of days for my Mac to decide I have enough disk space every time there's a new iOS SDK
The #reddit CEO Steve Huffman (spez) seemingly couldn’t read past this person’s first sentence without impulsively expressing his jealousy towards the app developers he’s screwing over like @christianselig’s #ApolloApp
Do I even want to know why every part of the submarine has the exact size, proportions, and even seam placement as the basic set of parts you get at the beginning of Kerbal Space Program?
“Users don’t really want federation, it doesn’t benefit them”
looks around at people forced to rebuild their followings because the single owner of their centralized social network did something bad and they can’t move to a different service without starting over
Officially one of the worst error messages I’ve ever seen. I’ve read it several times and still don’t know what it means, and I’m a software developer.
Some database (related to 1password???) is corrupt, 1password was “reinitialized” (implying… my passwords are gone?) so I should review my settings (what exactly am I supposed to review them for? Do I fix the corruption myself in… settings?), but it also says it's fine and I can keep using it? What???
In light of the #reddit CEO revealing he intends to sell users’ data to AI companies, and the recent findings that feeding AI-generated content back into AI training completely ruins it…
Wouldn’t the most effective protest be to edit our post/comment histories to replace them with ChatGPT-generated drivel?
Well, this is disappointing: it doesn't seem like the #SwiftUI scrollTransition modifier works with effects that apply Metal shaders (layerEffect, colorEffect, etc).
You can use one and it shows up, but it only renders the initial value and doesn't animate when the scroll phase changes. 🙃
#Javascript was a mistake. Allowing any form of scripting on web pages was a mistake.
(gumroad, a professionally developed, highly funded, commercial platform, just starts doing this on its own after you scroll down the page a little bit, no other user input required)
Am I the only one who thinks that instead of shutting off life-saving air conditioning during a heat wave, the solution should be to reduce NON-ESSENTIAL loads so people can cool their homes?
If you have a #SwiftUI app with a grid (e.g. LazyVGrid) or LazyVStack, how are you handling focus/keyboard navigation?
Wondering because it looks to me like just adding .focusable() to each item is all that’s needed for single selection…
but "The SwiftUI cookbook for focus" from WWDC23 says to add .focusable() to the grid view and then implement your own focus ring, keyboard navigation, & tap/click handling from scratch for each platform, which seems… brittle and not very SwiftUI-ish?
