7/2/2023 0 Comments 18g9323![]() What macOS version are you running specifically? Is it macOS 10.14.In the meantime, it would be helpful to know some details about your system. That being said, I’m also pretty confident that BetterTouchTool is not the culprit, as that’s also something I daily drove back on Mojave (and still use to this day on Monterey). (Basically, I’m replying here just to let you know that I have seen your post and will get back to you when I have the time to do so.) I can’t say I’ve been able to reproduce the issues you’ve described (and I was daily driving macOS 10.14.6 18G9323 for the longest time until I was forced to move off of it due to security updates no longer being released), but I will help you look into this further after I am done with finishing up a new update to TotalFinder for macOS 13. Word macOS Version 10.14.6 (Build 18G9323) Quartz PDFContext Microsoft Word - 19841115 Elie Wiesel In Modern Tales - The Fifth Son (1).docx Elie Wiesel. I’m aiming for a TotalFinder release next is indeed the last TotalFinder version for macOS 10.14 Mojave. They decided to redo it using this new system in Mojave. That is why it worked pretty well with TotalFinder. Finder thinks it manages its own individual windows but TotalFinder takes over and presents them within its own tabbed interface.Īnyways, historically Finder had its own tabs implementation which was “drawn inside each Finder window” and implemented prior “automatic window tabbing” existed. It is quite similar to what TotalFinder did to Finder. So they came up with a low-level “hacky” solution: the app still thinks it works with individual windows but macOS windowing server (and appkit) present groups of windows as tabs (showing the window associated with selected tab and hiding other windows in the group). Apple engineers wanted to allow automatic support for tabbing (ideally) without modifications to existing apps. In macOS 10.14 Finder implemented “automatic window tabbing” which is a feature added in macOS 10.12. It has been actually broken since Mojave. I spent two days reverse engineering the new behavior and I’m pretty confident I will be able to make it work again. Working around this is time-consuming, but even with this issue PDFPenPro has been an indispensable tool for my work. But I may be ignorant of some obvious reason why adding this functionality is difficult.) ![]() ![]() (Indeed this is what one does with Acrobat Pro. (This happens with Acrobat Pro.) If that is the case, a solution would be to implement an option of running OCR on a specified range of pages, so that a user can OCR a document not in one go but in smaller steps. My (technically illiterate) suspicion has been that, with larger files the memory runs out and causes the OCR process to halt. I can upload an example document which gives me grief, as well as a verbose log taken during an attempt at OCR-ing it. But this is unpredictable, and I often have to try a number of times. Selecting 'Locate Manually' and navigating to 'Install macOS Mojave.app' results in 'Unable to detect operating system'. Sometimes, one of the two “PDFpenOCR” dies and the other keeps going, and OCR is completed. Skipping to the second option - downloading the Mojave install package and selecting 'Install Windows or another OS from a DVD or image file' - Parallels attempts to find the install package and fails. Now using the HFS+ file system, they boot in 19 seconds. That has solved the TRIM 'problem' with my two Samsung 970s (NVMe SSDs) which, under Big Sur, could take up to 1 minute to boot. The application (PDFpenPro) itself thereby hangs, and I have to force quit it. I have written elsewhere that I am now running Mojave (10.14.6 - Build 18G9323) under HFS+ on my computer at left. What happens (which one can see from Activity Monitor is that one or two processes called 'PDFpenOCR' start when I run the “OCR document” command, and after a while these processes slow down, and eventually halt. I am hoping that the new support team at Nitro might offer further help. Tried current versions of browsers: safari, chrome, firefox. I have raised this issue a couple of times with the Smile support team. This has been a problem for me since before version 10. PDFpenPro's OCR process often stalls when being run on a relatively long document, whether it is run with the document open, or from the “OCR files…” command. ![]() I am using PDFPenPro 13.1 for Mac on MacBook Pro (13-inch, 2016, Four Thunderbolt 3 Ports), running macOS Mojave 10.14.6 (18G9323). ![]()
0 Comments
Leave a Reply. |