Post

Replies

Boosts

Views

Activity

Reply to Can DocC Generate Documentation for Extensions?
The solution is to use inside a package a public protocol with a type constraint and declare the type to conform to the protocol. Now you get the documentation you want. It is a cleaner solution than just using an extension. Example: import Foundation // The extension: public protocol FileManagerExtension: FileManager { } extension FileManager: FileManagerExtension { } // I don't know why this doesn't have to be public! // The new function: public extension FileManagerExtension {     /// My new function.     /// - Returns: 42.     func myNewFuntion() -> Int { return 42 } }
Oct ’21
Reply to ActionSheet & StackNavigationViewStyle constraint iPad bug
I have the same problem on iPad. Without navigation view style the action sheet ist displayed, but too much on the right side. With StackNavigationViewStyle() it is not displayed at all. <edit> It is only a problem when it is a trailing button. </edit> In both cases it prints an error like this:---2020-04-27 16:55:02.415121+0200 ***[1077:158890] [LayoutConstraints] Unable to simultaneously satisfy constraints. Probably at least one of the constraints in the following list is one you don't want. Try this: (1) look at each constraint and try to figure out which you don't expect; (2) find the code that added the unwanted constraint or constraints and fix it.( "<NSLayoutConstraint:*** UIView:***.width == - 16 (active)>")Will attempt to recover by breaking constraint<NSLayoutConstraint:*** UIView:***.width == - 16 (active)>Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.---(Added some *** in the log.)
Apr ’20