column

When trying to print an email with eM Client, the dialogue box pops up and the preview show the email's subject, To, and From lines in a long vertical column. This seems to only occur within the eM Client app and only on my Macbook Pro. I use the same email client on my Air with no issues. This is a recent development. I'm on Tahoe Beta 26.2.

Hi, We can easily get drive throughput using the iostat command, but it only outputs plain text that needs to be parsed, and I’m not sure if the format or column order is consistent across macOS versions. Is there any API that provides the same disk I/O metrics that iostat reports, but in a way that can be safely called from a notarized app?

I'm running a swift script that is emitting warning lines like this /Users/work/Documents/QuGame/QuGame/BoardTurnView.swift:1:1: warning: [dead-code] Debug-only symbol static SimpleTurn.== infix(SimpleTurn, SimpleTurn) -> Swift.Bool /Users/work/Documents/QuGame/QuGame/DataNotifications+PreviewData.swift:1:1: warning: [dead-code] Debug-only symbol DataNotifications.(addConversation)(to: QUBoardModel, local: GKPlayer, opponent: GKPlayer, texts: [Swift.String]) -> () /Users/work/Documents/QuGame/QuGame/DataNotifications+PreviewData.swift:1:1: warning: [dead-code] Debug-only symbol DataNotifications.loadBlankBoard() -> () These are correctly formatted for Xcode to detect the filename, line and columns. ` Showing Recent Issues [dead-code] Debug-only symbol static SimpleTurn.== infix(SimpleTurn, SimpleTurn) -> Swift.Bool [dead-code] Debug-only symbol DataNotifications.(addConversation)(to: QUBoardModel, local: GKPlayer, opponent: GKPlayer, texts: [Swift.String]) -> () [dead-code] Debug-only

I'm trying to create a UI with two button bars (top and bottom) inside the detail view of a NavigationSplitView, instead of using the built-in .toolbar() modifier. I'm using .ignoresSafeArea(.container, edges: .vertical) so the detail view can reach into that area. However, in macOS and iOS 26 the top button is not clickable/tappable because it is behind an invisible View created by the non-existent toolbar. Interestingly enough, if I apply .buttonStyle(.borderless) to the top button it becomes clickable (in macOS). On the iPad the behavior is different depending on the iPad OS version. In iOS 26, the button is tappable only by the bottom half. In iOS 18 the button is always tappable. Here's the code for the screenshot: import SwiftUI struct ContentView2: View { @State private var sidebarSelection: String? @State private var contentSelection: String? @State private var showContentColumn = true @State private var showBars = true var body: some View { NavigationSplitView { // Sidebar List(selection: $sidebarSel

At a high level, my app’s view hierarchy is a UISplitViewController, where the secondary column contains a UITabBarController that contains several UINavigationControllers. With this particular setup, I’m noticing every time a view controller is pushed, the navigation bar animation glitches. Notice how the back button and navigation title slightly slide left on each push, before abruptly resetting their positions. This issue only occurs when Liquid Glass is enabled. The issue does not occur if the UIDesignRequiresCompatibility key is added with a value of YES. I assume this is a UIKit bug, so I’ve filed FB20751418. But wondering if anyone is aware of any workarounds in the meantime as this animation glitch is quite distracting.

I'm using a NavigationSplitView on macOS which needs to show 2 or 3 columns depending on the selection of the sidebar. Column 1 has a list of main activities. Some of these just have some data to show and some have a sublist. Currently, when an item that has no sublist is selected, I set the 2nd column (content:) to: Spacer() .navigationSplitViewColumnWidth(0) This works, although it started hitting bugs requiring a workaround on macOS 26, which got me wondering, what is the correct approach here? NavigationSplitViewVisibility.doubleColumn is not the solution, as this hides column 1, not column 2.

We are using three column split view as root of our app and wants to hide the supplementary column alone in some cases and behaves like two column split view. With the existing apis we are unable to achieve this since it hides primary column as well and not giving expected results. .hide(.supplementary) setViewController(nil, for: .supplementary) But seen this behavior in Native Notes app when using the View as List and Gallery option. is there any way to achieve this with maintaining three column split view itself ?

When the Table container is scrolled up the data rows just keep moving up and become unreadable with the column headings superimposed over the top. Prior to scrolling upwards, the display will look like this. However, if you start to scroll up This behaviour does not seem to be the expected behaviour without any modifiers etc. The following is the code I have been using. import SwiftUI struct Customer: Identifiable { let id = UUID() let name: String let email: String let creationDate: Date } struct SwiftyPlaceTable: View { @State var customers = [Customer(name: John Smith, email: john.smith@example.com, creationDate: Date() + 100), Customer(name: Jane Doe, email: jane.doe@example.com, creationDate: Date() - 3000), Customer(name: Bob Johnson, email: bob.johnson@example.com, creationDate: Date())] var body: some View { Table(customers) { TableColumn(name, value: .name) TableColumn(email, value: .email) TableColumn(joined at) { customer in Text(customer.creationDate, style: .date) } } } } #Preview { Swi

Mostly a heads up, maybe this will help other people. I had a very simple test app for MacOS, just a ViewController with an OutlineView that had two columns, and the column data was initialized in awakeFromNib of the NSViewController like this: override func awakeFromNib() { if dataArray.count == 0 { dataArray.append( Node( firstname: John, lastname: Doe ) ) dataArray.append( Node( firstname: Mary, lastname: Smith ) ) } self.content = dataArray } There's also a toolbar with a button and a search field. This worked perfectly fine on Sequoia and Xcode 16, but since I updated to Tahoe and Xcode 26, if I try to run/debug the app from Xcode it hangs and eventually crashes. If Debug Executable is enabled in the scheme the crash is in libMainThreadChecker with EXC_BAD_ACCESS, and without debug it's a crash report with Thread stack size exceeded due to excessive recursion. I found that if I moved the self.content assignment inside the if block the problems went away: override func awakeFromNib() { i

Is anyone else using one of the Dark editor themes (such as Default (Dark) or Classic (Dark) in Xcode? And is anyone doing this with Xcode 26 on macOS 26? Here's the result while using the Default (Dark) theme while my Mac is in light mode: Note that the black background of the editor goes all the way to the far left edge of the Xcode window. The large gray area in the project tree is the black background bleeding through the sidebar. This is really distracting. Is there a way to fix this (besides not using a dark theme - I've been using dark themes for over 30 years)? This appears to be a poor design decision in macOS 26 to have split views show the background of the secondary column behind the primary column. iPadOS 26 has the same issue (see https://developer.apple.com/forums/thread/800073).