Posts

Post not yet marked as solved
1 Replies
331 Views
The PDFDocument class makes updating metadata attributes simple but appears to:Disallow arbitrary values for the /Producer attribute - the wite action substitutes an Apple string as the producerOffer no choice over the PDF version or the write format - it's 1.4, and compressed regardless of the original PDF formatAm I missing something simple in the PDFDocument class that will over-ride this behaviour?Is the PDFDocument structure archive conformant and, if so, to what level?Is it necessary to deal directly with CGPDFDocument to overcome these limitations?cheers,david
Posted
by enquora.
Last updated
.
Post not yet marked as solved
5 Replies
1.4k Views
Has anyone successfully used SwiftUI previews on a machine with a mechanical disk drive?Both the first and second betas of Xcode have been unable to generate previews on this installation.Results are any of a variety of errors, extraordinarily long compile times, inability to launch the simulator, a kernel panic or being logged out.An unmodified project created using the Xcode single-view template simply doesn't work.The experience is akin to using an ill-behaved Desk Accessory in System 7 :-(It's unclear whether the problem is with Xcode itself or the Catalina installation.Wondering if anyone has been through this and resolved the problem?
Posted
by enquora.
Last updated
.
Post not yet marked as solved
5 Replies
619 Views
The Software Update preference offered an update today after the announced release of the second beta but the preference's appearance is unfamiliar - a strange icon, no mention of which beta it is and the 'More info' link is, in fact, a web link which opens https://apple.com in the default web browser (at least someone is working on that - it actually uses the specified default web browser rather than Safari)!Pressing the Upgrade Now button did result in a 6.45 GB download but the installer immediatly complained about not being able to create (or update?) a recovery partition and quit.Has anyone successfully installed the upgraded the first beta to the second?Where is the downloaded installer saved to and is there a published checksum available anywhere to determine if the downloaded item is a valid installer rather than random garbage or a malicious payload?
Posted
by enquora.
Last updated
.
Post not yet marked as solved
1 Replies
825 Views
Filesystem performance on directories with non-trivial number of entires abysmal under Beta 3 and Beta 4. Finder rountinely locks up for many minutes at a time while listing directories, recursive deletion of files using command line takes minutes to hours with non-trivial directory nesting. Using a rotational hard disk, apfs.Problem is confined to a single profile.Booting to a separate volume on same disk with just a bare home directory has no performance problems.Problem home directory was populated using rsync from existing High Sierra machine (HFS+) — Migration Assistant was exhibiting same abysmal write rates (I'm guessing - estimated time to completion for 700GB was 100s of hours using 1000 BaseT direct connection).Is anyone else seeing this? Any suggestions on diagnosing problem? Submitting a radar is likely to elicit a reflexive request for a spindump — which is likely to take until release of beta 5 with current performance. I'd like more information before I file a report.
Posted
by enquora.
Last updated
.