JoshATA, It appears that the HSplitView is causing it. If you run the following, and change light to dark or vice versa in System Preferences, you see the "Test" button behave badly. struct ContentView: View {     var body: some View {         HSplitView {                        VStack {                 Text("Does this button change color correctly?")                 Button("Test") {                     print("Hi.")                 }             }         }         .frame(maxWidth: .infinity, maxHeight: .infinity)     } }

Hi "workingdogintokyo", Thanks for taking the time to do that. I'm running the newest non-beta stuff: macOS 11.2.1 and Xcode 12.4. So maybe that's the difference, and they've fixed it in the new versions. One other thing I didn't mention: I checked "SwiftUI App" when creating my test project, not "AppKit App Delegate". Other than that I changed nothing, besides the ContentView code I posted. I may also try a system restart. My MacBook's current "uptime" is 36 days.

Okay, good to know. If I go from light to dark, I get text that while not invisible, is still colored wrong (not enough contrast).

I reported a bug. FB9049107.

I'm seeing a similar problem. I'm trying to change the CommandGroup Buttons based to some state in an ObservableObject, and it's not happening. Did you ever figure this out? As you said, uses include: Showing a checkmark for boolean states, like "✓ Foo enabled" Items that show or hide parts of view. Eg, "Show Sidebar" ↔︎ "Hide Sidebar" Enabling or disabling items

It's obnoxious isn't it. What did you end up doing? I'm thinking of a few options... Include HTML in bundle, display in WKWebView within my app. Include HTML in bundle, send user to web browser to view. Include a PDF in bundle, send user to Preview or whatever to view it. Try a Help Book, even though the docs are 8 years old and I see lots of confusing posts online about it.

I don't know if this is a bug or what, but here is something that works. Add a level of indirection. Example: struct MyApp: App { @StateObject var appModel: AppModel = .init() ...     var body: some Scene {       WindowGroup { ... }.commands { CommandGroup(after: CommandGroupPlacement.toolbar) {     ItemsThatUpdate().environmentObject(appModel) } } ... struct ItemsThatUpdate: View {     @EnvironmentObject var appModel: AppModel     var body: some View {         Group {             Button(action: toggleFoo) { // Now this text will update as desired when model changes                 Text(verbatim: "Toggle Foo - \(appModel.foo)")             }             Button ... Button ...         }     }     private func toggleFoo() {         appModel.foo.toggle()     } }

This shouldn't be tagged with "SwiftUI". The Date type is in Foundation and the answer will be the same regardless of whether the app is using SwiftUI, AppKit, UIKit, or the command line.

Are you asking how to generate the list dynamically? Here is one way below. You can't have a for loop directly in the body of a SwiftUI view. Maybe in the future, but for now you have to use the ForEach thing. func makeTables() - [String] {     var result = ["Temporary"]     for i in 1...20 {         result.append("\(i) + \(i) = \(i+i)")     }     return result } struct ContentView: View {     var tables: [String] = makeTables()     var body: some View {         NavigationView {             List {                 ForEach(self.tables, id: \.self) { show in                     HStack {                         Image(systemName: "arrow.right")                             .resizable()                             .frame(width: 30, height: 20, alignment: .center)                         Text(show)                             .font(.custom("Chalkboard", size: 50))                     }                 }             }.navigationBarTitle(Text("Addition Tables (1 - 20)"))             .navigationBarTitleDisplayMode(.inline)         }     } }

If I look at the built binary in Finder (without doing a Clean Build Folder), it does have the updated icon. But running it uses the old icon in the dock and ⌘-Tab app switcher. Odd.

What is the code doing? Is it drawing to a CGContext as you would in a UIView.draw method? If so, it sounds like you have to use UIViewRepresentable to create a UIView that you can then use in a SwiftUI View hierarchy.

Sorry, I don't follow. There is no action: parameter for TextField, so what is would get triggered by the keyboard shortcut? I tried putting the modifier on it anyway, but the behavior is the same. TextField("Search", text: $searchQuery) { editing in .... } onCommit: { ... // still triggered by return OR focus loss }.keyboardShortcut(.defaultAction) I ended up using NSViewRepresentable and wrapping an NSTextField. So I have something working now, but I'd prefer to use pure SwiftUI if I can.

OOPer, I think you are being too nice, and have maybe too much patience. I would stop watching this thread, and if you like helping people here on the forums, spend time with others who respect your time, post code properly, and answer your questions.

robnotyou, your example with the ZStack partly works for me. The return key triggers the behavior, but the problem is the Button is still visible, as a small blue rounded rectangle, behind the (apparently transparent) TextField. I'm satisfied with wrapping NSTextField for now. It has some properties and delegate callbacks to more precisely control this behavior.

Workingdogintokyo, it sounds like maybe this has changed in macOS 11.3 beta. I'm running 11.2.3. I pasted your example into a fresh project, and here is the output I get when I start the app, click in the 1st text field, then click in the 2nd text field. changed 1 ---- commit 1