In our workflow, we frequently use the application “Pashua” to display more advanced dialog boxes. Recently, I discovered an issue on one user’s Mac where the Pashua dialog was not displaying as the front-most window. To troubleshoot, I created a new administrator account on the user’s Mac, and the issue was resolved—Pashua worked as expected, and the dialog boxes appeared in the foreground. This suggests that there might be a .plist or cache file in the user directory causing Pashua to malfunction. However, I haven’t been able to pinpoint the specific file or folder responsible. Has anyone else encountered a similar issue, and if so, how did you resolve it?
The last version of the now discontinued Pashua was released in May 2018. It was designed for Intel architecture Macs and might work on Apple Silicon Macs with Rosetta2 installed, or may misbehave because of its age and referencing frameworks that may have changed.
You could contact Carsten Blüm (email at that website page) and see if he will offer any insight into Pashua issues working on newer releases of macOS.
Thank you very much, VikingOSX, for the feedback and information. I may email Carsten as you suggested to see if he can offer any insight. However, the issue is currently limited to just one machine, so I wouldn’t consider it critical and would hate to waste his time. That said, the application itself works extremely well, and I’d hate to see it go away.
Keep in mind that although Carsten still has a Github site up where one can download and build (Intel) Pashua, there is no assurance that it remain available into the future.
The homebrew package manager indicates that owing to Pashua’s lack of upstream development, they consider it deprecated and it will be disabled from installation by them on July 5, 2025.
Understood, and that’s very good to know. I’ll eventually migrate away from using Pashua for dialogs and switch to vanilla AppleScript where applicable. As for the single machine experiencing the issue, I’ll most likely either clone it from a clean image or have the user create a new user folder. However, both options are time-consuming, which is why I posted the question on this forum—hoping someone might have encountered a similar issue and found a quicker or simpler solution.
Thanks again for your time and for being willing to respond to this one-off, non-AppleScript-specific question in the first place.