But doc describes how it is supposed to work. For instance: "In the following example of a simple login screen, when the user presses the Sign In button and one of the fields is still empty, focus moves to that field. Otherwise, the sign-in process proceeds."
That what it says if you read just the first line. A field being edited is focused, a field may be focused without being edited.
If you go through and make the effort to understand the examples, you will understand what they are. Sure, it is some effort, as for every learning… Good luck.
Thanks for the feedback, and great to read your app works now. As you get the log (RAMBar nil), that means the crash is just after, on the second print.
Thanks for the feedback. Note: you don't even need .searchable(text: $searchText). When TextField changes, State var searchText is changed, then body is reevaluated.
Performance is not the most critical aspect. RAM, disk space and screen size are, IMO, much more important. I work frequently on a 2015 iMac (3,3 GHz Intel Core i5 four core, so not a really powerful machine with today standards). I upgraded from 8 to 24 GB RAM (was much needed), got original 2 TB disk and 27" screen. It is perfect for Xcode development.
But doc describes how it is supposed to work. For instance: "In the following example of a simple login screen, when the user presses the Sign In button and one of the fields is still empty, focus moves to that field. Otherwise, the sign-in process proceeds."
That what it says if you read just the first line. A field being edited is focused, a field may be focused without being edited.
If you go through and make the effort to understand the examples, you will understand what they are. Sure, it is some effort, as for every learning… Good luck.
Thanks for the feedback, and great to read your app works now. As you get the log (RAMBar nil), that means the crash is just after, on the second print.
Thanks for the feedback. Note: you don't even need .searchable(text: $searchText). When TextField changes, State var searchText is changed, then body is reevaluated.
Performance is not the most critical aspect. RAM, disk space and screen size are, IMO, much more important. I work frequently on a 2015 iMac (3,3 GHz Intel Core i5 four core, so not a really powerful machine with today standards). I upgraded from 8 to 24 GB RAM (was much needed), got original 2 TB disk and 27" screen. It is perfect for Xcode development.