“column”

>> problem is solvedGood to hear.>> the name of the method is make, it's not a typoIn Swift 4, the name of the method is makeView, so perhaps you are using Swift 3? Anyway, it's not important, since you're clearly overriding the correct method.>> for all my other tables, I use a XIB file>> I can't use a XIB file fro the columns of this NSTableViewI think we are talking about two different things. I was talking about using a XIB file for just the NSTableCellViews, not the entire table. In principle, a cell view XIB can supply cells for one column or multiple columns, and one column can use multiple cell views.Your code to create the cells programmatically will (does!) work, but with the limitation that cells aren't automatically re-used like normal cells. This will have some impact on performance, but if the table is fairly small this may not matter to you.

@crystalminds in your example the app only shows 2 colums on every sidebar item, which is not the intended behavior. It should show the sidebar + 2 columns on sidebar item one and two. On sidebar item 3 there should only be the sidebar + 1 column. I have filed a radar/feedback for this and included all the information in this repository: https://github.com/JulianKahnert/NavigationExample

Xcode 14.0 beta 5 (14A5294e) seem to have fixed my issues with NavigationSplitView Fixed - Warnings Fixed - Selection of cell not happening (2nd time) in compact mode (For 3 column layout) - so no need to set the selected state of the middle column to nil onDisappear Hopefully it has fixed your issues as well, if not please file a feedback

I’d like all columns to have the same size. (Without providing an explicit, fixed size.)

Drag/drop from where, to where, exactly? Finder to storyboard, resource column to asset catalog? ...?

the name of the method is make, it's not a typo. If I use makeView, Xcode writes'makeView(withIdentifier:owner:)' has been renamed to 'make(withIdentifier:owner:)'You was right when you told me that I had no code to position the text field within the cell. So width and height were nul and it did'nt appeared. So problem is solved.But I wanted to tell you that I can't use a XIB file fro the columns of this NSTableView. My colum called ligne24 was just an example. I really don't know neither the names of the columns, nor how many columns will be displayed by this table.That's why I needed to override the make method.for all my other tables, I use a XIB file, of course.Thank's

Did you find the solution for that issue? How did you made the first column as sticky header in SwiftUI?

Settings > Notification > Music > Alerts Column > Un-tick “Lock Screen”

If you look at Quinn's example:let sheet: [[Int]] = [ [1, 2, 3], [4, 5, 6], [7, 8, 9], ]and compare it to a spreadsheet, it would look like this: A B C 1 1 2 3 2 4 5 6 3 7 8 9 If we add a 4th number to each row, the spreadsheet would look like this: A B C D 1 1 2 3 95 2 4 5 6 96 3 7 8 9 97which would correspond to:let sheet: [[Int]] = [ [1, 2, 3, 95], [4, 5, 6, 96], [7, 8, 9, 97], ]Columns are vertical, but there are no real columns as in a spreadsheet. Instead, every row contains all numbers in the row. It is still easy to get a certain cell (or element, as we call it), since you first get the row you want and then get the column you want from that.There is no limit per row of code, but the second column of the first row will always be the same, even if you add numbers at the end of the row.One thing to remember is that in Swift (and most programming languages), rows and columns start on 0, while they start on 1 in most spreadsheets. Is this what confuses you?

I have been given an api which outputs the followingYou should better add how you have output that JSON, which prevents some sort of easy misunderstanding.I assume it is the whole response from your API.And with pretty-printed: { statusCode: 200, headers: { Access-Control-Allow-Origin: * }, body: [ { ID: 29, ColumnAID: 12, ColumnB: Blah, ColumnC: , ColumnD: Not Listed, ColumnE: null, ColumnF: null, lat: null, lon: null }, { ID: 22, ColumnAID: 12, ColumnB: Blah, ColumnC: , ColumnD: Canberra, ColumnE: ACT, ColumnF: null, lat: null, lon: null }, { ID: 24, ColumnAID: 12, ColumnB: Blah, ColumnC: , ColumnD: Bondi Junction, ColumnE: NSW, ColumnF: null, lat: null, lon: null }, { ID: 25, ColumnAID: 12, ColumnB: Blah, ColumnC: , ColumnD: Broadway, ColumnE: NSW, ColumnF: null, lat: null, lon: null }, { ID: 26, ColumnAID: 12, ColumnB: Blah, ColumnC: , ColumnD: Castle Hill, ColumnE: NSW, ColumnF: null, lat: null, lon: null } ] } Outlined:{ statusCode: 200, headers: {...} body:

Great, thank you @sha921 ! However, the first column will not have the same size as the others. Any way to do this?

This worked for xcode - 12.2 beta and IOS 14.2 Untick Debug executable from below paths worked for me. Product -> Scheme -> Edit scheme -> Select Run (left column) -> untick Debug executable Product -> Scheme -> Edit scheme -> Select Test (left column) -> untick Debug executable Then close and run again.

Thanks so much, your first works great for me... But, how can I do the next step ? When I tapped on Landschaften that will be shows me Landschaften... That's nice. How can I do it for Maritimes? When I Tapped on Maritimes then I will that shows me Maritimes images... Can I drop more NavigationLinks in ContentView ? Have many Thanks ;) import SwiftUI struct ContentView: View { var columns = [GridItem(.adaptive(minimum: 160), spacing: 5)] var body: some View { NavigationView { ScrollView { LazyVGrid(columns: columns) { ForEach(ImagesList, id: .id) { images in NavigationLink { LandView() } label: { ImageCard(images: images) } } } .padding(10) } .navigationBarTitle(Text(Übersicht)) } .navigationViewStyle(StackNavigationViewStyle()) } } struct ContentView_Previews: PreviewProvider { static var previews: some View { ContentView() } }

Thank you for following up! For this specific problem, I'm wondering whether you need this column. For an interval schema like this (I'm assuming you are using an os-signpost-interval-schema here?), there is already a duration column that Instruments will generate for you. It will contain the duration in nanoseconds, but upon display in the UI, Instruments will format it into a reasonable unit (so e.g. 1,700,000 would be displays as 1.7ms). So maybe you can use the duration column as a workaround? In any case, if this bug is still happening to you, can you please file a bug report via Feedback Assistant? Please make sure to include an .instrpkg file with your schema + instrument definition that compiles, so we can check whether the problem maybe resides in a different part of the code.

OK, just for future reference, we call that the Comments column in Finder’s list view. There’s certainly no API to manipulate Finder views. On the AppleScript front, it seems like Finder has infrastructure to support this. For example: tell application Finder set visible of column comment column of list view options of Finder window 1 to true end tell Unfortunately I can’t get it to work. When I run the above on my machine (running 12.3.1) it doesn’t error but it also doesn’t do anything )-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com