From "Triggered" Script B, I want to "Resume" Paused Script A.

But putting a "Pause/Resume" step in Script B Pauses Script B rather than "Resuming" Script A.

The only Script B step I have found that will end the Pause in Script A is "Halt Script."

But this discards Script A's local context (variables, original layout, etc.),

requiring "globalization" of Script A's context if I want Script B to "complete" Script A's steps before Halting.

Am I missing another approach (without Plug-ins) to a Script B completion of Script A's Pause?

Here is my understanding:

If Script A contains a Pause (for controlled user input),

Script A is ONLY "Resumed" if the user

- clicks "Continue",

- presses "Enter", or

- utilizes a "Resume" button I add to the layout.

Now suppose:

- Script B is triggered during Script A's Pause.

- Script B "needs" to "Resume" Script A's Pause.

Here is my approach:

- Separate the remainder of Script A into Script C ("globalizing" context information as necessary).

- Use "Perform Script [script C]" as the only step after the Pause in Script A.

- Conclude Script B with these two steps:

- Perform Script ["Script C"]

- Halt Script // (to end/"Resume" the Pause initiated by Script A).

Is there a downside to this (other than needing to "globalize" the context information in Script A)?

Is there a better approach?

Thanks in advance!

Pausing scripts for user entry generally sucks. The button is ugly, it confuses users, and it's hard to develop around. There are other ways of limiting user choice. But I think you're missing one feature. In the setup of a button, you have the option of what to do with a Paused script. I'm not clear on how Script B is being triggered ( by a "script trigger" or user clicking a button?), but that may help.

I would do away with the Pause entirely. How to limit user choice depends on what you're trying to accomplish and you've got too much abstraction in your post to really understand what's going on.