I'm also seeing the same behavior on macOS 12.

Here's how to ensure that the hitbox for the context menu extends across the entire cell for all cells in the table view: Text("Item at \($0.name!)")   .frame(     maxWidth: .infinity,     maxHeight: .infinity,     alignment: .leading   )   .contentShape(Rectangle())   .contextMenu {     Button(action: {}) { Text("Action 1") }     Divider()     Button(action: {}) { Text("Action 2") }     Button(action: {}) { Text("Action 3") }   }

Have you tried wrapping request(action: .PSU, param: psu.name) in DispatchQueue.main.async in order to perform it on the next run loop?

Conform your view modifier to ViewModifier and Animatable explicitly.

It's impossible for anyone to answer your question if you don't include a reference to the source code of this app.

"As I know View in SwiftUI will get updated only if @Binding or @State values haven been modified." There are many more reasons why the View will be re-computed.

Also, this does not belong in the SwiftUI category.

If you're referring to the Console macOS app, then you should use the Logging framework.

Read the Supporting Sorting in Tables section of the documentation again. It recommends that you add an onChange modifier and perform the sorting there: .onChange(of: sortOrder) { sortOrder in clubs.sort(using: sortOrder) }

What are the similarities between Patient and Doctor that lead you to believe you should be using generics? What should the content of GenericView be if the fetch results are Patient vs Doctor? You should start by creating two separate concrete implementations of GenericView for each type of fetch result.

NavigationView {   Text("sidebar")   HSplitView {     Text("Primary View")       .frame(maxWidth: .infinity, maxHeight: .infinity)       .background(.blue)       .layoutPriority(1)     Text("Detail Panel")       .frame(maxWidth: .infinity, maxHeight: .infinity)       .background(.red)   } }

Try this: NavigationView {   Text("sidebar")   HSplitView {     Text("Primary View")       .frame(maxWidth: .infinity, maxHeight: .infinity)       .background(.blue)     Text("Detail Panel")       .frame(maxWidth: .infinity, maxHeight: .infinity)       .background(.red)   } } The background colors aren't even necessary. They just allow you to better visualize the bounds of each section of the HSplitView.

If you don't know the types of the array's elements in the "channel" at compile-time, then I would recommend that you convert them to the widest number type among all of the possible types in the channel. For example, if the channel could contain Int32 or Int64 number types, then your array in Swift should always contain elements of type Int64, because this is the wider type. Just convert values of type Int32 to Int64 when initializing the Swift array from the channel data.

What do you want to happen when the text cannot fit within the bounds of the UITextField?