Well, it’s been about a year since our marathon bug squashing efforts related to MacOS 14’s new approach to display containers…ahh good times.
However, as much fun as that was, I’m not super excited about repeating the experience
To that end, I was wondering if you have tested the current Scrivener build with Apple’s release candidate for MacOS 15.0. I’m assuming they aren’t meddling with displays again or anything else that might impact Scrivener since their primary focus appeared to be on AI this release.
That said, I was hoping you could provide some insight on the subject.
As always…much thanks for your efforts and the rest of the L&L team for making such a great product!!
I’ve been using Scrivener as part of my Sequoia beta testing and apart from Apple stealing the Writing Tools menu for Apple Intelligence haven’t stumbled across any issues. Keith’s already addressed that.
No doubt Keith will have been having a far more detailed look than me.
Thanks for the insight…it’s great to hear you haven’t run into any critical issues like the crash-boom-bash issues Apple created last time.
One question…what did you mean by your reference to the Writing Tools menu? I’m guessing I don’t use it, because I’ve never seen that menu in Scrivener. Did 15.x somehow prevent it from appearing?
Yep, Scrivener has been running fine for me in all my tests on Sequoia so far!
I haven’t experienced this in my tests yet, but admittedly I haven’t tried it on particularly long blocks of text. I’ll test it when I boot back into Sequoia shortly. I wonder if it’s a memory issue, given that proofreading can take a lot of processing.
It could possibly also depend on features in the text (footnotes etc). Have you tried it on a large block of text with no annotations, footnotes or other special formatting? Do you see a crash no matter what?
No special formatting. I don’t do anything like that. It works fine on small blocks of text, possibly a memory problem, although I am running it on a fairly powerful mac.
Have you tried them on the same large block of text, pasted into TextEdit? For best results, switch TextEdit to page view mode to cause it to toggle to the same version of TextKit that Scrivener is using.
Also another thing I can think of, is Scrivenings mode a factor in here? I wonder if maybe the internal dividers that separate sections might be a factor.
It doesn’t seem to crash in TextEdit, doesn’t find mistakes though, I can put in a half dozen and it might find one. Looks entirely different in every app. Finds more errors in Scriviner, but the interface covers up the mistake, so it’s kind of hard to tell what it’s doing. Doesn’t do that in other apps. Don’t think I’ll be using it until it’s gotten better.
