I have come across something with the Observation framework that is confusing me so if there are any #SwiftUI Observation framework experts out there that can explain this to me, I would be forever grateful. Why I don’t have to define the object as a State object?
@StewartLynch I’m no expert, but I think this still runs the risk of losing MyObject state by getting reinitialized when the view reinitializes. I think your example just doesn’t run into that happening? Unless you’re asking about Observation in general, which doesn’t need any property wrappers for the view to be able to observe and update.
@StewartLynch already answered by actual experts in the time I took to make my example 😅, but yeah, the Observable macro does all the wiring of the property to SwiftUI’s observation mechanism. The State property wrapper saves the value to the heap so it can be preserved across view initializations where the view's identity is unchanged. Embedding the counter in a parent view whose identity changes demonstrates this.
I just realized that if you're formatting to an abbreviated weekday then VoiceOver (at least Ava and Zoe Premium) will only fully pronounce some of the days.
I guess it's because the ones that aren't pronounced are actual words with other meanings? 🤔
Text(oneShowDay.formatted(.dateTime.weekday(.abbreviated)))
@ryanlintott I flip flop on that because sun.max is classified as "Weather" in the SF Symbols app and all of the other weather symbols have weather appropriate VO descriptions. But it does need to mean brightness higher in some scenarios.
@rafa I don't know about the specific problem, but my experience with SwiftUI is that when you try to use Apple’s "official” views, you will find many roadblocks and limitations; Still, you can build nearly everything pixel-perfect when you create your views from scratch.
So, my advice would be to not use a Toolbar but just a regular, custom SwiftUI view.
Back from sabbatical! More #CircuitPython and #SwiftUI content coming soon. Also info on how you can hire me to teach a bootcamp on these concepts or teach to faculty, leaving course material for use in their own classes. Feel free to share if you know educators who may be interested. https://youtu.be/DM8DUx1LkVg
@rafa@davidbures from memory that would make it work like a HStack, so yeah centered if you place it between two Spacers. Wait, you want a single button to fill the entire width of the Toolbar?
I wonder, is there a built-in AppKit/SwiftUI component that lets you show a folder structure like this? Or do you have to create a custo one? I can't think of a way to look this up 🤔
WWDC24 is right around the corner. Before the excitement and rush of what's to come, I want to share some navigation fun facts and tips. None of this is new, having been discussed previously in sessions, etc. From talking with developers, these are parts of the system that are often overlooked, or forgotten about #21DaysOfSwiftUINavigation#SwiftUI This is all running on macOS Sonoma 14.4, Xcode 15.3
List selection can drive navigation pushes. You can populate the selection binding with a value-destination NavigationLink, or, any other way you would normally populate it. #21DaysOfSwiftUINavigation#SwiftUI
A video showing a compact NavigationSplitView on iPhone Previews next to a code sample. The preview shows a list of with 4 elements, 3 navigation links, and 1 Text row. All 4 rows get a grey highlight when active. The non-navigation link row, the simple tagged Text, has no chevron, but still highlights gray in sync with the push progress. Code: import SwiftUI enum Sports: String, Hashable { case pickleball case dance case archery case volleyball } struct Day1: View { @State private var selection: Sports? var body: some View { NavigationSplitView { VStack { List(selection: $selection) { NavigationLink("Pickleball", value: Sports.pickleball) NavigationLink("Dance", value: Sports.dance) NavigationLink("Archery", value: Sports.archery) Text("Volleyball").tag(Sports.volleyball) } } } detail: { if let selection { VStack { Text(selection.rawValue.capitalized(with: .current)) Image(systemName: "figure.(selection.rawValue)") } } else { ContentUnavailableView( "Make a selection", systemImage: "volleyball") } } } } #Preview { Day1() }
NavigationStack and NavigationSplitView are intended to be used statically — establish the structure of your scene and generally don't move them around (there are some exceptions). Don't push a NavigationStack as part of a navigation destination. SwiftUI tries to warn in logs when it detects this.
At the risk of teaching ChatGPT anti-patterns, here is an anti-pattern! Don't try this at home, or anywhere else you take your MacBooks. #21DaysOfSwiftUINavigation#SwiftUI
@ctietze@uliwitness There are other super crazy design decisions. PartialFormatter class that doesn’t conform to the Formatter protocol. The fact that their actual PhoneNumberFormatter does, but needs a „generatedPhoneNumber = true“, because its default mode is NOT doing formatting to PhoneNumber (and it silently fails in SwiftUI Textfields). And there is a Class called „Formatter“ in the framework that is not Foundations’ Formatter. (1/2)
I love coffee, so I got a nice machine a while ago. Trying new beans means dialing in everything and considering all the nuances. I got tired of taking notes all the time, so I started building a small app that ideally replaces this little notebook.
Reacting to network status changes in SwiftUI doesn't have to be complicated. By converting NWPathMonitor into an AsyncSequence, you can handle updates efficiently and cleanly within your views. Discover how in my latest post:
I’m working on a project with an important launch animation that only plays on the first launch. Unfortunately, when people install the app via TestFlight, the “what to test" sheet obscures the animation. Has anyone found a way to detect when the sheet is dismissed? #SwiftUI
@michaelsteeber I haven’t verified this yet, but I’d check Environment .scenePhase and restart the animation when transitioning to ScenePhase.active.
Even if it doesn’t solve your specific TestFlight sheet issue, it’d be a nice addition in the case where someone launched the app and got interrupted by something else/locked their phone/whatever.
In SwiftUI, you can 👉concatenate Text views👈 with different styles and still apply common view modifiers! For example, you can change the foreground style of Text views individually but group them to set a common font style! 😎
@bde dang! I see no issue with it, seems to work flawlessly as SwiftUI only sets the presenting value to false. Now I wanna do some refactoring! (I still use the deprecated method as the annotation is wrong and Xcode doesn’t show the warning)
I got most of the way through this ambient sound app last summer, and I may finish it once my current collaboration is in the App Store. I really like the icon for this one!
#swiftUI Question: I am using AnchorPreferences. Is there any way to use multiple AnchorPreferences at once? Like, use an array of points and communicating it up the hierarchy, but using a collection of [Anchor<CGPoint>] instead of the single Anchor<CGPoint> that the .anchorPreference modifier hands over?
@ctietze This is what I am doing. Essentially the whole „Anchor“ thing is just a fancy way of bubbling up geometry values in the „global“ CoordinateSpace, and it’s converted back at the point of use. I can do the whole ting myself by „convention“ thtat the points I use are global, but I’d rather do it with Apples wrapper that makes it explicit – if I can.
