Posts

Showing posts from May, 2022

Acrobat "design", part 1

Image
 Adobe's "design" of Acrobat is even worse than Microsoft's Word!  The above is clip of the error you get when trying to run OCR on a signed document. One would think that Acrobat could tell you the specific problem (a signature) rather than some generic warning of "not permitted".  It's also completely unclear why low memory/disk space would cause an operation to be "not permitted". Not possible, maybe, but not "not permitted". Also of particular note is that checking the box to "Ignore future errors" does *not* work. Meaning, if you try to run OCR on a large signed document, you'll be clicking on the OK button from the error message for *each page in the document.* Force close it is. SaaS is a bad joke.

Microsoft "design", part 1

Image
There are many things I don't understand about Microsoft's Windows design/implementation. One is security. Why does Windows warn me that a scan is due, rather than ... just performing the scan?  As built, a user needs to A. notice the small triangle exclamation point in the notification area, B. click on the notification to open "Security at a glance", C. note what the actual error is (here, "Quick scan due"), D. click on <Scan now>, E. finally, click the <Quick scan> button.   This flow is nonsense. The only good thing that arose from this blog post was buried deep in the flow, where I noticed:   Same thing. What the hell, Microsoft? I'm connected to the internet. Update the protection definitions already, in the background, without user input. Then do the quick scan, without user input. This isn't hard.   Update 1 : I ran the quick scan. Interesting. Windows claimed the scan would take around 15 seconds. The timer clicked down to about