I know that the JXA scripts and some of the manually triggered object/stencil scripts can prompt for basic input beyond the message box demonstrated in the online automation docs, but what I’d really like the ability to do would be to prompt for key parameters that would drive behavior of some of the plugin’s actions directly from the plugin code itself.
Some of this I know I can get around via using listeners for events on properties, but I was wondering why there wasn’t any kind of direct interaction beyond the yes/no/cancel message box included in the API.
I’d really prefer not to have a bifurcated application that drives some behavior from externally and some from within the context of a given drawing simply because of limitations in the scripting API. It’s much harder to maintain and the UX is potentially dreadful depending on what kinds of things need to be done.
Can anyone shed some light on this?