column

I am having the same issue with the Column N.A. How can we solve this?

I have some potential progress, but due to the nature of this crash, I don't know if this is correct or not. After inspecting the sqlite-files that represents the backingdata, I discovered that a property backed by an integer was set to null after migration even the original value was 3. Upon inspection, I realized this was the very first property I ever migrated, so it was still annotated with @Attribute(orginalName: propertyName), even tho the migration which crashed for me was the 9th migration step overall for the app. Thus, with the Schema I was migrating from being: struct SchemaV7 { @Model class Item { @Attribute(originalName: propertyName) var newPropertyName: Int } } And then removing it in the destination Schema: struct SchemaV8 { @Model class Item { var newPropertyName: Int } } made me able to complete the migration without crashing. Wether this was the solution or not, I have no idea, but it could explain some of the crashes I've seen earlier... The property which was crashing the app have never b

Filtered columns behave like Swift ArraySlices. In particular they maintain the original indices, see ArraySlice, Slices Maintain Indices. You need to replace for i in 0 ... data.rows.count with for i in data.rows.indices. The other option is to convert the slice back to a regular DataFrame: let data = DataFrame(data0.filter { ... })

Hi Ziqiao, thank you for the suggestion. I tested using exclusionPaths instead and interestingly, the bug still occurs! I can send you the version of the project that uses exclusionPaths instead of different container sizes if you'd like to compile/run and see. For convenience, here is the changed code in question with exclusionPaths: setupLayout() changes to: func setupLayout() { var index = 0 for textViewData in PreviewTestData.textViewDataArray { self.ensureContainer(with: textViewData.frame.size, exclusionPath: textViewData.exclusionPath, at: index) index += 1 } } ensureContainer(...) changes to: @discardableResult private func ensureContainer(with size: CGSize, exclusionPath: NSBezierPath?, at index: Int) -> NSTextContainer { precondition(index >= 0 && index <= layoutManager.textContainers.count) if index == layoutManager.textContainers.count { let container = NSTextContainer(size: size) container.widthTracksTextView = false container.heightTracksTextView = false container.lineFragmentPa

Hi Ziqiao, thank you for looking at the project and for the feedback. My word processing app requires containers of differing width in order to fulfill its core functions. I know Apple's own Pages app supports documents that flow continuously with varying numbers of columns with widths that the user can set arbitrarily. And Apple's own documentation of NSLayoutManager / NSTextContainer mentions multi-column text (https://developer.apple.com/library/archive/documentation/TextFonts/Conceptual/CocoaTextArchitecture/TextSystemArchitecture/ArchitectureOverview.html#//apple_ref/doc/uid/TP40009459-CH7-SW4). Text Kit 2 doesn't yet support more than one text container, so that's not an option for me yet and I can't migrate to Text Kit 2 until they support container / page breaks. I would love for this issue to be elevated. This is an actual and serious bug in Text Kit!

MusicKit isn’t gated by an entitlement. That’s why, when you enable it on an App ID, you enable it in the App Services column rather than the Capabilities column. Enabling it there grants that App ID access to that service without needing your app to be signed with any entitlement. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I'm sharing the code that parses my preview data here. I'm using an NSViewRepresentable and the call to - paginator.exhibitTheBug() - is within makeNSView(...). But note that this bug occurs whether I call paginator.exhibitTheBug() there, or in updateNSView(...), or from textStorage(:didProcessEditing:...) via a DispatchQueue.main.async closure. I.e., I thought at first that it was a threading/runtime issue, but it's not. class Paginator { let textStorage: NSTextStorage let layoutManager: NSLayoutManager init(textStorage: NSTextStorage, layoutManager: NSLayoutManager) { self.textStorage = textStorage self.layoutManager = layoutManager self.setupLayout() } /// Runs the functions that will exhibit the bug. func exhibitTheBug() { // Get char range to measure in container. let characterRangeToTest = self.getCharacterRangeOfFirstColumnType() // The bug occurs in this call: testMeasurement(for: characterRangeToTest) } /// Returns the effective range of the text storage over which the column type (`NSAttrib