“column”

Hi There, I have found a suspicious memory leak when I use Scroll View, List or anything else to list a View. This is Scroll view with Lazy Grid define: struct TravelingView1: View { var body: some View { ScrollView { LazyVGrid(columns: [GridItem(.flexible())]) { ForEach(0..<10) {_ in Rectangle() .frame(height: 20) } } } .frame(height: 200) } } And Button Style in the View as: struct ScreenView1: View { @ObservedObject var drawRadioButtonViewModel: DrawRadioButtonViewModel1 var body: some View { RadioButton(type: .radioButton, toggle: drawRadioButtonViewModel.isRadioCheck, identifier: Quick Split, radioWidth: 302, action: { [weak drawRadioButtonViewModel] in drawRadioButtonViewModel?.updateToggleCheck() }, label: {}) .offset(x: -CGFloat(100)/2, y: CGFloat(100)) Button(drawRadioButtonViewModel.isRadioCheck ? Checked : Unchecked, action: { [weak drawRadioButtonViewModel] in drawRadioButtonViewModel?.updateToggleCheck() }) .offset(x: -CGFloat(100)/2, y: CGFloat(100) + 30) } } With Button Style as: st

Should this not set the inspector width to 550 every time? TableView() .inspector(isPresented: $state.presented) { InspectorFormView(selection: model[state.selection]) .inspectorColumnWidth(min: 150, ideal: 550, max: 600) } This is almost verbatim from the WWDC video (10161). This ideal parameter will be the size of the column at at first launch, but if the user resizes the inspector, the system will persist that size across launches. Inspector uses the minimum width (150) in every case. How can the ideal width be guaranteed upon initial launch? I could set the minimum to 550, but I'd like the user to be able to reduce the size of the inspector as well ... Thanks much & keep inspecting!🧐 (Sonoma, beta 5 / Xcode beta 6)

Xcode indexing will cause my Mac Mini (M1) to crash when indexing is active (ON). ===> Xcode Version 12.5.1 (12E507) To test the following, I created a smaller OSX desktop application, compared to my main OSX desktop application, which is significantly larger in scope, and size. That said, I enter the following code in the terminal to activate and deactivate Xcode Indexing: 1. Indexing is active (ON) when applied in the terminal : defaults write com.apple.dt.XCode IDEIndexDisable 0 2. Indexing is NOT active (OFF) when applied in the terminal : defaults write com.apple.dt.XCode IDEIndexDisable 1 The application causing the crash with Xcode Indexing turned (ON), creates a PList file for my main application to use, which is an array of dictionary tuples. This application for the moment, creates a baseline array of 4,000+ dictionary objects with eight (8) tuple objects per dictionary. I use the same design with different, and significantly less information to create other PList array of dictionary objects, suc

I am working with data in Swift using the TabularData framework. I load data from a CSV file into a DataFrame, then copy the data into a second DataFrame, and finally remove a row from the second DataFrame. The problem arises when I try to remove a row from the second DataFrame, at which point I receive an EXC_BAD_ACCESS error. However, if I modify the timings column (the final column) before removing the row (even to an identical value), the code runs without errors. Interestingly, this issue only occurs when a row in the column of the CSV file contains more than 15 characters. This is the code I'm using: func loadCSV() { let documentsDirectory = FileManager.default.urls(for: .documentDirectory, in: .userDomainMask).first! let url = documentsDirectory.appendingPathComponent(example.csv) var dataframe: DataFrame do { dataframe = try .init( contentsOfCSVFile: url, columns: [user, filename, syllable count, timings], types: [user: .string, filename: .string, syllable count: .i

I am learning SQLite queries. I use prepare statement and one or more calls to a step statement. The prepare statement knows the pointer to the database, the UFT8 select statement and the name of the pointer which will point to the complied SQL select statement. The first step call runs the compiled select statement and if data is returned, the first row is made available via column calls. It seems logical to me that the select statement returns all matching rows but if the first step statement only has access to the first row of data, the balance of matching rows must be stored somewhere. Is this the case and if so where are the query results stored? Or is does this work in some other manner?

Hi, I'm testing one of my app on iOS 14 with Xcode 12 beta 3 (12A8169g) and I have a problem with my storyboards. Xcode give me this error for all the storyboards that contain a split view controller: An internal error occurred. Editing functionality may be limited. The log generated by the Xcode Report a bug button say: Exception name: NSInvalidArgumentException Exception reason: UITabBarController is unsupported as viewController for -[UISplitViewController setViewController:forColumn:] in Primary column It worked correctly on Xcode 12 beta 2. Has anyone encountered the same problem and found a way to fix it? Thank you

Hi,i have been trying out SwiftUI Table and wanted to present a details view when click on Table Row occurs, but I couldn't figure out how to deselect row once its been selected, while it may not be what Table was intended for, but I still think this code should be valid. (iPadOS) struct Person: Identifiable { let givenName: String let familyName: String let emailAddress: String let id = UUID() } private var people = [ Person(givenName: Juan, familyName: Chavez, emailAddress: juanchavez@icloud.com), Person(givenName: Mei, familyName: Chen, emailAddress: meichen@icloud.com), Person(givenName: Tom, familyName: Clark, emailAddress: tomclark@icloud.com), Person(givenName: Gita, familyName: Kumar, emailAddress: gitakumar@icloud.com) ] @State private var selectedPeople: Person.ID? @State private var detailsViewPresented: Bool = false var body: some View { Table(people, selection: $selectedPeople) { TableColumn(Given Name, value: .givenName) TableColumn(Family Name, value: .familyName) TableColumn(E-Mail Address, va

Hello, I am turning to this forum because I suspect I am doing it wrong when it comes to implementing VoiceOver accessibility in my collection view. I suspect this because the system has resisted everything I have tried to do, fought it tooth and nail, and I can't see any way to get this to work. The Collection View I have a collection view that displays a large dataset. It uses a custom collection view layout to create a spreadsheet-like view. It has hundreds of rows, and each row can have hundreds of items. The items in each row do not conform to specific column widths. Their width is defined by the data they display, and for the purposes of this discussion, can be considered to be arbitrary. To the left of the table is a column of sticky headers whose position remains fixed in relation to the content. On top of the table is a row of headers, whose position also remains fixed. The Problem The default accessibility behavior that Apple has baked into UICollectionView is completely impractica