Buy the man a coffee

Thank you Andrew

Thanks for the info! I have not looked at EventKit at all, but I will add it to my list.

As you will see, this is a requirement for CloudKit for relationships, This comes later Another reason might be wicked be if there was no cascade delete on a book, then your could have an orphan quote. I don’t understand your second question however. If your model has any property’s that are linked to another model, then you need a relationship. That would be either one to one where, one to many, or many to many.

@@StewartLynch I think you answered my question. One of my model property is linked to another model. Here are my updated models after seeing this video. Yet to try it out but hopefully it is correctly setup. What do you think? @Model class ShowModel { var name: String @Relationship(deleteRule: .cascade, inverse: \SeasonModel.show) var seasons: [SeasonModel] = [] init(name: String, seasons: [SeasonModel] = []) { self.name = name self.seasons = seasons } } @Model class SeasonModel { var season: Int var episodes: Int var show: ShowModel? init(season: Int, episodes: Int = 0) { self.season = season self.episodes = episodes } }

Glad it was helpful!

Very welcome

It is all worth learning 😀 Titles are tough to describe the content. What about the description. Plus I always do a short intro at the beginning saying g what the video is about.

These new APIs are conveniences. They save us from the headache of creating our own states and Timers, counting down the time etc.

That would be unwise because you might have people who have not used your app since the first migration so a lightweight migrtion woud not work for this. YOu would have to use a full migration strategy here. I have yet to do a video on that topic, but it is a good one so I will do that later this year.

I am happy that you think so

Can you set the object that is passed in to the detail screen to nil so that the ContentUnavailble view is displayed

@@StewartLynch The ContentUnavailableView does display in "SIDEBAR" as soon as all items are deleted in the array. But the DETAIL screen some how retains the last selected item from sidebar. Hard to put in words.

You are most welcome

Not that I am aware of

You're welcome!n

I would not use this framework any more. Instead, use the native Charts framework for SwiftUI. I have several videos on this topic.

Thanks! 😃

Thanks

I could say the same for you Mark. You have a way with words and images that are not matched by anyone.

@@StewartLynch Yes, Mark's tutorials are easy to understand with little bit of fun I agree!

Thanks for pointing that out. I never noticed that. It is definitely the shadow that is causing it. I would just remove the shadow. It appears that a shadow on a clipShape is janky

No need

@@StewartLynch how about using nodejs to deal with backend logic?

I just downloaded the completed project from this video and updated the deployment target to iOS 18 and using Xcode 16, I could see no issue. The clear button still works.

@@StewartLynchThanks for the speedy reply! I downloaded the completed project and using my minimum deployment iOS16.2 and XCode 15.4, the clear button works as you described/intended. However, when I changed the textfield line from: TextField("Enter Integer Number", text: $intNumberString), to TextField("Enter Integer Number", text: $intNumberString), axis: .vertical) the clear button (the image "multiply.circle.fill") does not appear.

@@vloggymcvlogface OK. You are right. That breaks it. You could remove that line in the view, and surround the Content in the view modifier with an HStack and add your own clear button there. HStack { content Spacer() if !text.isEmpty { Button { self.text = "" } label: { Image(systemName: "xmark.circle.fill") } .foregroundStyle(.secondary) } }

@@StewartLynch With a small modification your suggestion works just fine: 1. the xmark did not go away when the field was not in focus, so I created a new FocusState boolean which I passed to the viewModifier to set the opacity of the xmark to 0 when the field did not have focus. Also I tried changing the HStack to a ZStack to get the xmark inside the textfield but I couldn't figure out how to prevent the inputted text from overwriting the xmark. An issue for another time... Thanks for your help and I love your other videos. Also thanks for suggesting Fireside Swift - I have listened to all their podcasts FWIW I wrote my code in FortranIV in 1970 and I still love coding. Cheers John

@vloggymcvlogface what I don’t really understand is why you would need a vertical access for a numeric text entry. Would it not always be on a single line?

The context handles it for you.

What version of Xcode?

Thanks for this. Yes, over the years, things change and it is unfortunate that one cannot update a video on RU-vid.

You are absolutely right. My fingers know what I am doing, but my brain does not always. Thanks for pointing this out. It is the option key that will get the full parameter list, not the command key.