{"id":33278,"date":"2021-07-30T15:13:01","date_gmt":"2021-07-30T19:13:01","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=33278"},"modified":"2021-07-30T15:13:01","modified_gmt":"2021-07-30T19:13:01","slug":"implementing-a-focusable-text-field-in-swiftui","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/07\/30\/implementing-a-focusable-text-field-in-swiftui\/","title":{"rendered":"Implementing a Focusable Text Field in SwiftUI"},"content":{"rendered":"

Gabriel Theodoropoulos<\/a> (via Dave Verwer<\/a>):<\/p>\n

What I mentioned above is definitely good news, but it regards evolvements that are going to be working in macOS Monterey and above. That’s nice, but what about backward compatibility? What if we wanted to make apps that support macOS versions prior to Monterey, such as Big Sur or Catalina?<\/p>\n

The answer to these questions is what this post is all about. In the following parts, I will take you step by step through the implementation of a custom text field capable of:<\/p>\n

  1. Getting the focus automatically when a view appears; that means that the text field will be ready to start typing into without clicking on it first.<\/li>
  2. Moving the focus on subsequent text fields by pressing the Tab key.<\/li><\/ol><\/blockquote>\n\n

    I still find it surprising—or maybe not, since it was designed for a device with neither a mouse nor a keyboard—that it took three releases for SwiftUI to get the equivalent of firstResponder<\/a>, one of the most basic Cocoa concepts. Maybe in a few more years it will support setting the nextKeyView<\/a>.<\/p>\n\n

    Jonathan Wight<\/a>:<\/p>\n

    < 400 lines of SwiftUI<\/p>\n

    That said I can’t figure out how to layout a resizable username\/password login dialog without hardcoding widths or breaking causality.<\/p><\/blockquote>\n\n

    Rob Napier<\/a>:<\/p>\n

    \n

    The paradox of SwiftUI.<\/p>\n

    I find it utterly infuriating and incredibly promising.<\/p>\n<\/blockquote>\n\n

    Previously:<\/p>\n