ExtendScript Toolkit hangs on every run

Forum|Forum|5 years ago
February 8, 2021
2 replies
584 views

I am using 64-bit Windows 10 and FrameMaker 2019 and 2020 (64-bit). When I click the run button in ExtendScript, the script runs and finishes normally, but ExtendScript hangs for a few seconds and give me a "Not Responding" message. Sometimes it will happen again when I click in the script's window to continue editing. Saving the script sometimes hangs it for a few seconds too. Does anyone else experience this? Should I switch to Visual Studio Code or something else? It is quite frustrating that Adobe doesn't maintain and update their scripting tools.

Scripting

This topic has been closed for replies.

K.Daube

Community Expert

Should I switch to Visual Studio Code or something else? It is quite frustrating that Adobe doesn't maintain and update their scripting tools

Yes, this is really frustrating... See your other post - nothing has changed since then.

However, I have other complaints with VS Code - but with all these problems I'm still much faster, because there are no such deleays built in. It just looses the connection to the Extension Host quite often. But even closing VS Code, restarting it etc. does not take that long as waiting in ESTK for an ordinary close ...

J

J.Kahl

Known Participant

And here I was thinking, I would miss something, using wrong preferences or being plainright stupid. But when Framemaker scripting legends like you, Rick and Klaus, encounter the same issues, it might not even be my fault...

In addition: Is the ESTK also extremely slow once it is linked to the app that it was made for? I can watch the letters appear one after another when I start typing and ESTK is linked to FrameMaker 2019...

J

J.Kahl

Known Participant

preferences = settings
I cannot find the "edit" button. Maybe I AM kinda slow today...

Klaus Göbel

Legend

I experience the same thing.
Sometimes this happens to me when I am debugging. Then the screen goes pale and I have to wait for a longer time until I can continue working. Sometimes I also have to exit ESTK and I am not able to save the script anymore.
I will not switch to Visual Studio Code, because that means too much effort for me. I guess I will have to live with it.

It seems that Adobe neither develops the ESTK further, nor fixes errors. But this problem seems to be Microsoft's fault (.NET).
I would like to have more planning security regarding the future of ExtendScript.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded