I’d appreciate another video. I’d like to have a solid understanding using buttons and actions in SwiftUI. Thanks, your videos are very helpful and much appreciated ✌🏼

Really good explanations, very good examples of SwiftUI. I am continuing the next episodes. Thanks.

Yes I would be interested in seeing this through to completion. Whether that’s the calculation portion, the landscape portion, etc I’d like to see it recreated as much (and as accurately) as possible.

Great Lesson in SwiftUI Thank you Brian

I like this way of learning. Thank you.

Thank you for the content, It's been exciting to follow along. But, I would appreciate it if you continue and complete the project.

Yes, would love to get the calculations part!

new upload time I like it

Good one. Thanks Brian :)

great tutorial please make full course on swiftui advance topics also

11:00 You can simplify the CalculatorButton enum by giving its cases Integer raw values. Then in the switch statement for the title var, check if the rawValue is ≤ 9. If so, convert the raw value to a string and return that.

well done, it's been a great session, thank you

Yeah wanna c the calculation part was waiting for it since ep1

How about combine all the number cases into a single case with an associated value? This will reduce the repetitive code for backgroundColor and title. Example use of button: let button: CalculatorButton = .number(value: 4)

Thank you

Yes please continue, I want to see the calculation part

Once your enum conforms a RawRepresentable (string in this case) tu can directly assign a custom rawValue as: case one = “1”, two = “2”.....

thanks for this great tutorial, here is my solution: func buttonWidht(_ button:CalcButton? = nil) -> CGFloat { if let b = button, b == .zero { let standard = (UIScreen.main.bounds.width - 5 * 12) / 4 return 2 * standard + 12 } return (UIScreen.main.bounds.width - 5 * 12) / 4 } func buttonHeight() -> CGFloat { return (UIScreen.main.bounds.width - 5 * 12) / 4 }

Very nice SwiftUI intro tutorial! I'd only change the calculation for the button size, as using func buttonWidth -> CGFloat can be misleading and you even had to duplicate code in order to make .zero work. An alternative would be return a CGSize(width, height), and set the values in your buttonWidth func. :)

Brian, can you make video related to combine framework in details perhaps. Please.

Nice video. 👍🏻 Can you please do the calculation part ? It’ll be very nice. Thank you

Great content brian thank you for the video! Will you still be doing UIKit courses or just mostly Swift UI from here on out?

Hey Brian, thanks again for the great video again! Waiting for the next one ;-) Just a quick question about buttons. I have managed to create a button with repeat via Timer.scheduledTimer. In this class i have defined a #selector referring to @objc func but when i put this construct in a separate class file, i got an error... argument of '#selector' cannot refer to global function. (placed in the viewcontroller gives no error btw) Any pointer in the right direction would be great! Thanks!

It would be nice to complete this serials with action on buttons. Thanks!

You should try using VSCode for the tedious operations like duplicating lines and for stuff like your huge case statement.

You can add the "plusMinus" button by pressing "Shift + §" on your Mac. The "§" key is via the top left corner near escape.

It was a nice tutorial. Can you make a video on the push to new Screen using Default NavigationView and a Custom Navigation View in SWIFTUI?

Here's a question: If I wanted to programmatically change the display value of one of the buttons, how would that work? I ask because I am trying to figure out out to build a fixed-size matrix of buttons (not unlike the calculator example) which will contain (display) values that will change in my app.

Great content, but I have only one problem with it If you are building an iPad or macOS app, UIApplication.main.bounds.width returns the screen size, not the app size When multitasking this can lead to wrong sizes You should use GeometryReader instead

For the `0` button just duplicate the function and return what he pasted in the height: func buttonHeight(button: CalculatorButton) -> CGFloat { //__________ return (UIScreen.main.bounds.width - 5 * 12) / 4 } And make sure you also keep the width function too: func buttonWidth(button: CalculatorButton) -> CGFloat { //__________ if button == .zero { return (UIScreen.main.bounds.width - 4 * 12) / 4 * 2 } return (UIScreen.main.bounds.width - 5 * 12) / 4 } Then pass them in the frame: .frame(width: buttonWidth(button: button), height: buttonHeight(button: button)) /*.....................................................................................................................................*/ and also instead of doing a title computed property, just do it in the cases directly: enum CalculatorButton: String { //__________ case decimal = "." case zero = "0", one = "1", two = "2", three = "3", four = "4", five = "5", six = "6", seven = "7", eight = "8", nine = "9" case equals = "=", plus = "+", minus = "-", multiply = "X", divide = "÷" case ac = "AC", plusMinus = "\u{00B1}", //

I have used Struct ... struct CalButton : Hashable{ var text : String var color : Color }

Can we use struct instead of enum and differentiate while preparing!!!

🙏🙏🙏

Did you read the swift books published by apple cover to cover

Please can help me to build custom keyboard for deaf “signs keyboard “

Couldn’t you name the enum case variable as it’s string representation? So then you wouldn’t have to do that title variable?

Another easier way to define the size of the zero button: var widthBottons: CGFloat { switch self { case .zero: return 156 default: return 70 } } .frame(width: botton.widthBottons, height: 70, alignment: .center) .cornerRadius(50)

wow - SwiftUI is awesome, but very slow on my mac mini i5 2014. I was planning on upgrading to the latest i5 and 32GB. Hopefully that will help.

If you're going to educate people make sure you are doing that close to perfect: 1. Make use of specifying the rawValue instead of providing title to serve exactly the same purpose 2. move your button frame calculation to the CalculatorButton and make to return the actual frame

Why not just an array of objects with the params for color ect. Still good tutorial. Looks like Swift finally changed to not use solely storyboards. Thank god

i need continue :)

You speak like a radio host, sir. Great video though.

I don’t understand the reason you would lay out 14 out of 16 buttons with their correct labels. It seems monumentally lazy and a bit irresponsible. It would have taken all of 5-10 seconds to finish it up correctly. Taking shortcuts like this when building out interfaces is a poor habit to get into. It creates a high likelihood that one will “forget” to go back and finish it later - often resulting in apps that ship with errors. If it’s about “just demonstrating the concept” and saving time, one row of buttons would have been sufficient - but by the time you do 14 of them, it makes less than zero sense why you would abandon the last 2. 🤦🏻‍♂️ 🤷🏻‍♂️