Robert Hahn
Robert Hahn
To whom it may concern that have custom `Codable` struct/class and looking for workaround (using the example of `NSRect`): ```swift extension NSRect: Defaults.Serializable { // TODO: A temporary workaround for...
I have recently developed a custom MeasurementField that takes an optional `configuration` to directly access the AppKit properties: https://gist.github.com/Maschina/f391b3ed8e5d45389e72fbe95d290f00 We may add something like this...
I have made a first try by adding the following to the UIKit+Extras.swift: ``` elseif os(macOS) import Cocoa internal enum IBInterfaceKeys: String { case styleName = "SwiftRichString.StyleName" case styleObj =...
> Also, in general, you should just use the default size. It's sized to fit any keyboard shortcut, but also no wider than necessary. @sindresorhus I see a use case...
> How should we proceed here? It's probably easiest if I do the smaller linting fixes, right? Yes, makes more sense this way.
By the way, you can easily reverse to `group.PDFArchiverShared`, if you revert the commit [c8ff785](https://github.com/PDF-Archiver/PDF-Archiver/pull/156/commits/c8ff785b083611366326b754c329625f3ab00a2f)
#337 fixes this issue
@Jeehut I agree with your decision to not maintain two different frameworks as long as iOS 16 is not yet irrelevant. Regarding Swift 6.0 compatibility, I was primarily referring to...
I am just realizing that event streams also require observations. Will make another commit for that.