Use watermarks to identify draft or confidential in-house documents, assert copyright, or clarify intended distribution.Īpply header and footer text with options for customizing page position, font, and page range. Version 10 introduces watermarks, headers & footers, and for Pro users, batch OCR (Optical Character Recognition).Īdd text and image watermarks with opacity and rotation controls, as well as custom page range options. San Francisco, CA – Ap– Smile, the developer of productivity applications for Mac®, iPhone® and iPad®, launches PDFpen and PDFpenPro 10.0, a new major version of its all-purpose PDF editing tool for Mac. I believe I pulled this script without the handlers from this forum post. This script checks if a PDF needs to be OCR'd, OCR's the PDF if needed, then closes PDFPenPro if the only document open in PDFPenPro is the target PDF. Here is the script I am using (handlers included) in case this will be helpful for anyone else. Everything is working properly now that I have the correct AppleScript handlers in place. Well, then I guess I'm just a little nuttier (or at least more forgetful) than I thought. EDIT: I also just tried creating the script from scratch as a new file (copy and pasted the script text into a new file to avoid any file permissions issues by duplicating the file directly), deleting the rule and creating it manually, then tried to run the new rule and I'm seeing the same error from Hazel when trying to execute the external script. Any thoughts on what could be the issue? I can run it as embedded if that is the only way I can use AppleScript moving forward, but I would much rather have a centralized, external file I can edit to update multiple instances of the script in Hazel simultaneously. I've also reset Hazel, the Script Editor, and PDFPenPro with tccutil and granted their permissions again when prompted to try to rule out that issue. Could there be some issue with the TCC framework not granting proper control to Hazel, or perhaps I missed a prompt to allow Hazel to run the script externally? There are no unchecked items in the Privacy prefs for anything related to Hazel or the Script Editor. I was prompted to allow Hazel to control PDFPenPro as expected, but then ran smoothly. The script runs properly when run as an embedded script. As MasterRee Posts: 19 Joined: Mon 8:21 pm PDFPenPro 12 opens and OCRs them without issue if done manually, or by running the AppleScript with the alias manually specified like so: set theFile to alias "Users::Desktop:Screen Shot at 7.03.13 PM.pdf" Any ideas on what could be the issue? There have been no updates to PDFPen Pro on my Mac and I don't recall this issue occurring only after the macOS 12.4 update or a recent Hazel update. 21:38:58.533 hazelworker DEBUG: Error reading file /Users//Library/Application Support/Firefox/prefs.js: Error Domain=NSCocoaErrorDomain Code=260 "The file “prefs.js” couldn’t be opened because there is no such file." UserInfo= 21:39:02.680 DEBUG: Timer scheduled for folder /Users//Library/Mobile Documents/com~apple~CloudDocs/Archive/Scans at 00:00:00 +0000 21:39:02.682 DEBUG: Thread 0圆00003e60c00: Task removed: Tested with different PDFs and still the same results. When I attempt to run the script through Hazel on the same PDF I get OSAScriptErrorNumberKey = "-1708" in this output in the log while in debug mode: Code: Select all 21:38:58.471 DEBUG: Thread 0圆00003e60c00: Run worker for folder: /Users//Library/Mobile Documents/com~apple~CloudDocs/Archive/Scans 21:38:58.497 hazelworker Running worker (v5.1.2) for folder with identifier: 16777220-2972009. I have uninstalled and reinstalled Hazel and reset the PPPC permissions for Hazel and the Automation (Apple Events) permissions category using tccutil, but the issue persists. I can run the script directly through Script Editor and it works precisely as intended (except that I have to specify what "theFile" alias points to. I haven't been able to identify any change prior to Hazel failing to launch PDFPenPro to run OCR. In my case I have: Hazel 5.1.2 macOS 12.4 PDFPenPro 12.2.3 The script has been working fine since my update to Monterey back on 12.0 or 12.1. Hello, I'm having virtually the same issue and the same script with PDFPenPro.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |