Learn everything you need to know about SwiftUI's new Bindable property wrapper. I will show you the problem that it solves, and why it doesn't replace @Binding by any means.
КОМЕНТАРІ: 37
@maDM728 місяців тому
Great content, keep going! The only thing - PLEASE remove the background music. That extra noise really makes it hard to listen to you, especially annoying if you watch at 1.5-2x speed (which I often do). Check how the Fireship channel does the narration without almost anything but his voice, and that's great. Thanks and good luck!
@tattooedpierre6 місяців тому
Concur on the BG music.. or at the least make it far quieter.
@hdsenevi4 місяці тому
I second this comment as well. BG music is super distracting. That said, awesome video and keep them coming. Thanks for doing this. Please lower or remove background music on future videos
@DonnyWalsdev3 місяці тому
Thanks! I've uploaded a new video with the bg music far lower, it's the most recent one on the channel so feel free to take a look. The reason I've included it is because to me narration with complete silence is rather boring and lots of channels I watch do have very mild music playing in the background. I might end up removing it in future videos but I want to give it a few tries to see if there's a sweet spot.
@mario_luis_devМісяць тому
agreed. The background music is just obnoxious. Without it the video would be 10x better
@timnewton43396 місяців тому
Thank you very much. I've watched a number of videos introducing @Bindable, but none have been so clear to explain its purpose (with such a simple example) as yours.
@DonnyWalsdev3 місяці тому
Thanks!
@jcteo17 місяців тому
That really cleared things up for me. Thanks!
@Noem010 місяців тому
Really good video. Good explanation and on point for the new Observable Features from iOS 17. Thanks
@RobertHolzapfel2 місяці тому
When I just thought that video could not be any better, you brought the issue with @Environment after 11 minutes on the table: AWESOME! Thank you so much for this video. I spent a whole day and night with that nightmare error message "can't find controller in the scope", which was exactly the situation that you describe here (in my case 'controller' is kind of a viewmodel). So, this video came to rescue me, although I found it very late. Thanks again !!! 🤩
@shuodeng38312 місяці тому
Thanks, finally understand the bindable
@iosmayank10 місяців тому
Welcome to UKposts Creator life, Donny🎉 Nice video.
@qkrotor2 місяці тому
Nicely explained. I would say the music is a little distracting and doesn't add anything IMO.
@DonnyWalsdev2 місяці тому
Thanks! i do like to have some sound in the background instead of pure silence so in my latest video I brought the volume down by a lot. It's an ongoing experiment for the moment
@cub7118 місяців тому
Nice video, that I will come back to every time I mess up this. How can you use this without importing Observation? (Or SwiftData which also includes observation)
@DonnyWalsdev3 місяці тому
Unfortunately you can't
@yourbestsail9 місяців тому
All fine. You should just improve audio and microphone. Sound is everything, especially in this kind of videos.
@DonnyWalsdev9 місяців тому
Thanks! I'll definitely try and improve that for the next one(s)
@NouvelEmpire2 місяці тому
ultra interesting
@DonnyWalsdev2 місяці тому
Thanks!
@obelix84777 місяців тому
Yes, please. Do not add background music.
@victorriurean6 місяців тому
@user-jz8op2dc4eМісяць тому
Why can you input content in the canvas preview? How do I set it up?
@DonnyWalsdev19 днів тому
You can start "playing" the canvas from the previews UI and that should make it interactive
@angrypi9 місяців тому
why does @bindable only work for `class` type?
@DonnyWalsdev9 місяців тому
Probably because reference semantics are needed to ensure that you can actually observe a specific instance instead of having multiple separate copies that would get out of sync.
@dre56718 місяців тому
@State is no longer required with @Observable macro on your model/view model 🎉. Since the model is now observed, watching for changes, it will efficiently update the views the are using any property outputting change
@DonnyWalsdev8 місяців тому
That's true for the observation part. But if you want the observable model's state to correctly be persisted you need @State to prevent SwiftUI from making a new instance every time your view struct is initialized. Note that this is only the case if you _own_ the observable in the view. Views that receive the instance in their init can indeed use a plain let/var
@roym2716 днів тому
I had to stop watching because of the background music - it’s not great when you’re narrating as I was unable to focus on what you were saying.
@DonnyWalsdev15 днів тому
I'll probably do a re-record of this video at some point without the bg music. It's a shame that it's not possible to "update" a video without a full reupload
@lapusan20086 місяців тому
Thank you! I was looking for a solution to the exact same problem you have addressed. Environment -> @Bindable
@danstoian77216 місяців тому
10:33 One question, at line 11, you have @State on a class, should that not be @StateObject instead? And if not, if that's all done. Is there any longer a need for @StateObject?
@helgessons6 місяців тому
If I understood it correctly from another source, it seems like before there was a memory leak with using @state with a class but now with iOS 17 that has been fixed and it's now recommended to use @state instead. However I'm not 100% sure so please double check yourself as well :)
@DonnyWalsdev3 місяці тому
@StateObject should be used for instances of ObservableObjects that you create in the view. So if a view creates an ObservableObject instance that you want to observe, you use @StateObject. When you're using the new @Observable macro, the SwiftUI view will observe your object no matter what. You use @State in order to make sure that the Observable instance you create persists when SwiftUI makes new instances of your view in response to model changes. Without @State you'd end up with fresh instances of your Observable every time a new view struct instance is created (which can be quite often)
@khaledsh85064 місяці тому
So basically, replace @EnvironmentObject with @Bindable
@DonnyWalsdev3 місяці тому
No, an environment object is an object that conforms to ObservableObject and lives in the environment. An @Bindable property allows you to bind to properties of an Observable instance because without it yu can't bind at all. The environment and @Bindable both solve very different problems so you can't replace one with the other