I've noticed Text Checker is very unresponsive when opening it and navigating the lists of issues in text fields with a lot of flagged issues. I'm writing an Interactive Fiction game with Inform 7, and it's very useful for detecting words where I hold down the shift key too long and capitalize multiple letters. Is anyone else experiencing this problem? I wrote to Apple, and hopefully this can be fixed. I'm using an M4 Mac mini running 15.3, so there should be more than enough processing power. Even if there are a lot of issues, I expect it to take 2 to 3 seconds, not the 10 or 15 I'm observing.
Comments
Voiceover can't do large…
Voiceover can't do large bodies of text. No idea why. Doesn't work in word, pages, etc. I'm talking novel length though which is probably a fringe enough issue that apple don't really give a monkeys.
VO can't manage large…
VO can't manage large/complex amount of anything :) just with 10 pages and less than 4000 words it struggles.
Has it not always been like this?
I remember writing a 28 page essay for an English writing class in college, using Pages, this would've been back in like 2014, or 2015, it was a pretty decent paper for the most part. It was about the history of accessibility in technology, and why MainStream technology would do better to have accessibility imported into it, rather than the old tried and true, "made for the blind".
Anyway, I remember Pages choking on that when I was doing my proofreading/editing.
As I say, I think it's such…
As I say, I think it's such a fringe event that apple accessibility doesn't really take it seriously. Most people who are dealing with large documents are likely in a professional setting and using windows. I use Ulysses for my writing as I can break documents down in to chapters. Really it is something to report to apple but, as it seems such a no-brainer, a text editor should be able to process text, that I'm certain they are aware of it and don't consider it worth the resources.
Search affected as well
If I have a big document in TextEdit, for example, and do a VO-F search there, it always results in "TextEdit not responding" messages. Even after a long waiting period, nothing works.
LAst Saturday, I dealt with a big .log file containing log records, around 50MB raw text, and when I tried to search for something using VO-F, TextEdit no longer worked until I force quit it.
I wonder if using the…
I wonder if using the command F search will work better as that is built into the editor rather than using voiceover's flaky search function.
But 50mb of raw text is…
But 50mb of raw text is everkilled even on windows screen readers. The windows 10 notepad would start slowing down with just 6mb, while the windows 11 one is more robust. Agree though that just with 100k characters in text edit VO start his equivalent of kernel panic.