While upgrading from a legacy extension to a UXP panel, I ran into a bit of a showstopper.
A handful of commands have now been gated behind a requirement for a “modal scope”. Examples include app.bringToFront(), the make document batchPlay command, etc.
https://www.adobe.io/photoshop/uxp/ps_reference/classes/photoshop/#batchplay
Part of our workflow involves listening to secure websocket commands from external sources, and reacting to those commands to create documents, download images, create new artboards, etc.
Gating those behind modals every time will prove to be a subpar user experience.
Unless I’m missing something, I’m not sure there’s an elegant way around this (nor, do I expect, is there intended to be).
Can we add a feature that, similar to the session tokens for accessing the disk, asks the user if the plugin can modify the state of photoshop and allow these types of commands?
If there’s something I’m missing here as well, please let me know!
Example failed batchPlay command:
