Messages that note a C function is about to be called, rather than a higher level UnrarKit or Cocoa method, end with ".", since it's not expected for them to log any details of their own.Log messages don't have final punctuation (like these list items).Log messages should follow these conventions. If you think you spot one, open an issue or a pull request! Logging They were written after the initial round of log messages were, so there may be some inconsistencies (such as an incorrect log level). These are the general rules governing the particulars of how activities and log messages are classified and written. The available levels, in order of increasing verbosity, are default, info, debug, with debug being the default.
Sudo log config -mode "level:default" -subsystem When debugging your own code, if you'd like to decrease the verbosity of the UnrarKit framework, you can run the following command: You can view messages at the Info or Debug level to view more details of how UnzipKit is working, and use Activity Tracing to help pinpoint the code path that's causing a particular error.Īs a fallback, regular NSLog is used on older OSes, with all messages logged at the same level. Loggingįor all OS versions from 2016 onward (macOS 10.12, iOS 10, tvOS 10, watchOS 3), UnzipKit uses the new Unified Logging framework for logging and Activity Tracing. Documentationįull documentation for the project is available on CocoaDocs. You may need to right-click and open it in Finder to get through Gatekeeper the first time you do so. It's only ever verified to run in the simulator, but if you provide Team info, it should probably also run on-device.įor large file extraction, the tool uses the rar executable. Included in the source repo is a project named "UnrarExample", that builds as part of the main solution. To open in Xcode, use the UnrarKit.xcworkspace file, which includes the other projects.
It will cause the operation to fail, returning nil or NO (depending on the return type, and give an error with error code URKErrorCodeUserCancelled. Using either method above, you can call to stop the operation in progress. [extractFilesProgress addObserver: self forKeyPath:observedSelectorīOOL success = [archive extractFilesTo:extractURL.path NSString *observedSelector = NSStringFromSelector( localizedDescription)) Static void *ExtractFilesContext = &ExtractFilesContext If you don't have a hierarchy of NSProgress instances, or if you want to observe more details during progress updates in extractFilesTo:overwrite:error:, you can create your own instance of NSProgress and set the URKArchive instance's progress property, like so: Using your own explicit NSProgress instance [extractDataProgress addObserver: self forKeyPath:observedSelector NSString *observedSelector = NSStringFromSelector( fractionCompleted)) URKArchive *archive = initWithURL:aFileURL error: nil] Static void *ExtractDataContext = &ExtractDataContext
0 kommentar(er)
