What am I doing wrong here? Is it perhaps a bug, or is this drawing just not possible on macOS? I can paste the full code below if needed. The PDFDocument appears as before, except without the custom drawing.īy contrast, on iOS/Mac Catalyst, both of these methods reproduce the custom drawing.
Using PDFDocument’s dataRepresentation() to convert the document to Data and then using init(data:) to turn it back into a PDFDocument. The file is successfully saved with all elements except the custom drawing. Using PDFDocument’s write(to:) to save to a file. The problem is that using either of the methods below will result in a document that contains all the expected elements, including PDFAnnotations, with this exception regarding the PDFPage subclass’s draw(with:to:): The original page can be drawn/removed by adding/removing super.draw(with:to:), but any other drawing in this method is not preserved, despite appearing correctly in the PDFView. Further, if I insert the PDFDocument’s pages into a new PDFDocument using insert(_:at:), the PDFView will display the second document with the custom drawing. (I tried flipping it, but it did not solve my problem below.)Īfter the PDFDocumentDelegate is set, the PDFView correctly displays the pages with custom drawing. To adapt the sample, I cut out UIGraphicsPushContext(context), UIGraphicsPopContext(), and the code required to flip the context, as its orientation was already correct. I adapted the Custom Graphics iOS sample code (), which appears possible on macOS based on this evidently successful 2018 example. I am attempting to add custom page drawing in a PDFDocument on macOS. That means if Xcode 13.1 requires Monterey on Intel Macs, we're going to be blocked from updating to the latest Xcode for quite awhile, which is problematic because (if Xcode 13.1 behaves like all the past updates we've seen) it means we won't be able to debug our app with devices running latest iOS versions.
#Change mac address no root apk torrent update
It usually takes them three or four months after a new major macOS release to roll out an update to all our Macs, due to the usual delays in how long it takes our anti-malware suppliers and all the validation and testing our IT department performs on the updated system image before major updates. For example, I have to wait until my corporate IT department officially supports the new OS before I can update my Mac to it. If it does indeed affect Intel Macs as well, this could be a huge blocker for many of us who work within large enterprise and use managed computers. Is that correct or does that requirement only affect Apple Silicon users? However now it seems Xcode 13.1, which is now in RC, will require us to already be on macOS 12 Monterey. It wasn't until Xcode 12.5 that we finally had to all be on Big Sur. Traditionally Apple has always waited until mid-cycle (Feb./Mar.) before releasing an Xcode update that requires the latest macOS.įor example, Xcodes 12.0 through 12.4 on Intel Macs would work on Catalina. Will this requirement also affect the official release of Xcode 13.1? It seems Xcode 13.1 RC requires the unreleased macOS 12.
0 kommentar(er)
