Chapters
Chapters

Chapters

Hide chapters

iOS Apprentice

Eighth Edition · iOS 13 · Swift 5.2 · Xcode 11

Before You Begin

Section 0: 3 chapters
Show chapters Hide chapters

Getting Started with UIKit

Section 1: 8 chapters
Show chapters Hide chapters

Checklists

Section 2: 12 chapters
Show chapters Hide chapters

My Locations

Section 3: 11 chapters
Show chapters Hide chapters

Store Search

Section 4: 12 chapters
Show chapters Hide chapters

Getting Started with SwiftUI

Section 5: 3 chapters
Show chapters Hide chapters

Checklists

Section 6: 8 chapters
Show chapters Hide chapters

12. Add Item Screen
Written by Eli Ganim

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

Heads up... You’re accessing parts of this content for free, with some sections shown as scrambled text.

Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now

Now that you have the navigation flow from your main screen to the Add Item screen working, it’s time to actually implement the data input functionality for the Add Item screen!

Let’s change the look of the Add Item screen. Currently it is an empty table with a navigation bar on top, but it should look like this:

What the Add Item screen will look like when you’re done
What the Add Item screen will look like when you’re done

This chapter covers the following:

  • Static table cells: Add a static table view cell to the table to display the text field for data entry.
  • Read from the text field: Access the contents of the text field.
  • Polish it up: Improve the look and functionality of the Add Item screen.

Static table cells

First, you need to add a table view cell to handle the data input for the Add Item screen. As is generally the case with UI changes, you start with the storyboard.

Storyboard changes

➤ Open the storyboard and select the Table View object inside the Add Item scene.

Changing the table view to static cells
Dyublorz xpo qapso ciij ri tsiwud dintz

The table view has a section with three static cells
Xbo bipno yuuf fav a datyaob wufd gdfoo fjayom tuvkl

The table view with grouped style
Qwo viflo zeez lebw yyeikup hfzce

Adding a text field to the table view cell
Ogxulf o moyr jiimg ba lye yehto paix vinr

You can now type text into the table view cell
Noe jet caj ghbu days ewdo rjo hihsi xuiy loqh

Disabling cell selection

Look what happens when you tap just outside the text field’s area, but still in the cell (try tapping in the margins that surround the text field):

Whoops, that looks a little weird
Rlouws, jbaq weokv e lajrcu biidn

// MARK:- Table View Delegates
override func tableView(_ tableView: UITableView, 
          willSelectRowAt indexPath: IndexPath) 
          -> IndexPath? {
  return nil
}

Returning to sender

You’ve seen the return statement a few times now. You use return to send a value from a method back to the method that called it.

override func tableView(_ tableView: UITableView, 
      numberOfRowsInSection section: Int) -> Int {
  return 1
}

override func tableView(_ tableView: UITableView, 
      numberOfRowsInSection section: Int) -> Int {
  return "1"
}

override func tableView(_ tableView: UITableView, 
      numberOfRowsInSection section: Int) -> Int {
  return items.count
}

override func tableView(_tableView: UITableView,
            cellForRowAt indexPath: IndexPath) 
            -> UITableViewCell {

  let cell = tableView.dequeueReusableCell(
                    withIdentifier: "TheCellIdentifier", 
                               for: indexPath)
  . . .
  return cell
}

override func tableView(_ tableView: UITableView, 
          willSelectRowAt indexPath: IndexPath) -> IndexPath? {
  return nil
}

@IBAction func addItem()

func configureCheckmark(for cell: UITableViewCell,
                       with item: ChecklistItem)

func methodThatDoesNotReturnValue() -> ()

func anotherMethodThatDoesNotReturnValue() -> Void

Reading from the text field

You have a text field in a table view cell that the user can type into, but how do you read the text that the user has typed?

Adding an outlet for the text field

When the user taps Done, you need to get that text and somehow put it into a new ChecklistItem and add it to the list of to-do items. This means the done() action needs to be able to refer to the text field.

Click the toolbar button to open the Assistant editor
Mxogh hra saoqyut jifvuk ca efib myi Oynaztity uqidiv

The Assistant editor
Cfi Algiswabv etimez

Control-dragging from the text field into the Swift file
Hijfpop-ckaxkipt znaf yxi dezn soizc oybe hwe Tsoyg sozo

The pop-up that lets you add a new outlet
Njo may-ax ktop nuyh xoo adh o cov oablek

@IBOutlet weak var textField: UITextField!

Reading the contents of the text field

Now you’ll modify the done() action to write the contents of this text field to the Xcode Console, the pane at the bottom of the screen where print() messages show up. This is a quick way to verify that you can actually read what the user typed.

@IBAction func done() {
  // Add the following line
  print("Contents of the text field: \(textField.text!)")

  navigationController?.popViewController(animated: true)
}

Contents of the text field: Hello, world!

Polishing it up

Before you write the code to take the text and insert it as a new item into the items list, let’s improve the design and workings of the Add Item screen a little.

Giving the text field focus on screen opening

For instance, it would be nice if you didn’t have to tap on the text field in order to bring up the keyboard. It would be more convenient if the keyboard automatically showed up when the screen opened.

override func viewWillAppear(_ animated: Bool) {
  super.viewWillAppear(animated)
  textField.becomeFirstResponder()
}

Styling the text field

With that in mind, let’s style the input field a bit.

The text field attributes
Rci sorw biotj iryhunixus

Handling the keyboard Done button

➤ Make sure the text field is selected and open the Connections inspector. Drag from the Did End on Exit event to the view controller and pick the done action.

Connecting the text field to the done() action method
Fecmopqing cdo buyr heawp mu hva duza() epveit gebdih

Viewing the connections for the done() method
Foahoxp vte fompaxxouhx tuf mpe teli() zofpuv

The keyboard now has a big blue Done button
Xsu cajguuwb bus yuy i biv dtuu Guxu qusdiq

Disallowing empty input

Now that you have user input working, It’s always good to validate what the user entered to make sure that the input is acceptable. For instance, what should happen if the user immediately taps the Done button on the Add Item screen without entering any text?

The Auto-enable Return Key option disables the return key when there is no text
Sho Uuqo-utozro Quxavz Cer itpuob giguzlob yhi qisafz dep wsos nviyi ac xo sinc

Becoming a delegate

Delegates are used everywhere in the iOS SDK, so it’s good to remember that it always takes three steps to become a delegate.

class AddItemViewController: UITableViewController, UITextFieldDelegate {
Drag from the Connections inspector to connect the text field delegate
Kguq tbis vso Yepqaccuavy enwyipdex ro rusgadg qqo tuvk yaekd nucawijo

Configuring the Done button

You also have to add an outlet for the Done bar button item, so you can send it messages from within the view controller in order to enable or disable it.

@IBOutlet weak var doneBarButton: UIBarButtonItem!

// MARK:- Text Field Delegates
func textField(_ textField: UITextField, 
               shouldChangeCharactersIn range: NSRange, 
               replacementString string: String) -> Bool {

  let oldText = textField.text!    
  let stringRange = Range(range, in:oldText)!
  let newText = oldText.replacingCharacters(in: stringRange, 
                                          with: string)
  if newText.isEmpty {
    doneBarButton.isEnabled = false
  } else {
    doneBarButton.isEnabled = true
  }
  return true
}

let oldText = textField.text!
let stringRange = Range(range, in:oldText)!
let newText = oldText.replacingCharacters(in: stringRange, with: string)

if newText.isEmpty {
  doneBarButton.isEnabled = false
} else {
  doneBarButton.isEnabled = true
}

doneBarButton.isEnabled = !newText.isEmpty

if some condition {
  something = true
} else {
  something = false
}

something = (some condition)

Fixing issues

One problem: The Done button is initially enabled when the Add Item screen opens, but there is no text in the text field at that point. So, it really should be disabled. This is simple enough to fix.

The Done button is not enabled if there is no text
Hcu Buzu pupwuy ed jog ovuhhob ak lhoza in ga bonr

The Clear Button
Hhi Tleeh Fejcen

func textFieldShouldClear(_ textField: UITextField) -> Bool {
  doneBarButton.isEnabled = false
  return true
}

Using FileMerge to compare files

In case you’re stuck on a particular bit of code and don’t know what you did wrong, you can always refer to the provided source code for each chapter. However, given that there’s potentially a fair amount of code to go through, you might not know how to find what is different between your code and the provided code.

11. Navigation Controllers
13. Delegates & Protocols
Have a technical question? Want to report a bug? You can ask questions and report bugs to the book authors in our official book forum here.
© 2025 Kodeco Inc.

You’re accessing parts of this content for free, with some sections shown as scrambled text. Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.

Unlock now