A while ago (2017-01-23) I issued bug report FRMAKER-2240
Although all my scripts include the directive #target framemaker, and it is my habit to first open FM and then ESTK to start a script, the script runs into an error, because ESTK does not look at the directive. It tries to execute the script in ExtendScript Toolkit CC.
The bug report is stil "To track" - imho a lazy excuse. Please vote if you have the same problem with this as I have.
It works for me using ExtendScript Toolkit CC. If the directive is just #target framemaker or #target FrameMaker it does switch from the ESTK to the last used version of FrameMaker. When the FrameMaker version is included like this #target framemaker-14.0 it opens the specific version of FrameMaker. I've tried this with all ExtendScript enabled versions of FrameMaker.
My ESTK is version 184.108.40.206
Hi Klaus, I haven't seen this problem either. The #target framemaker directive works for me here with 220.127.116.11. -Rick
Well friends, I have tested:
How are the debugging target interactions set in your ESTK preferences? I have this:
On my system I changed the Auto Launch Application... from the default value of not selected. Otherwise everything else is as installed.
I only have a problem with the script directive when there is some incompatibility with what the script expects to be available. So, for example if I have a script that expects to work on the current document, but there is no document loaded yet, then yes, the script may fail.
When I run a script with a directive it always just starts the relevant FM version. It just provides a small dialog to cancel the app start.
I never have a problem with the directive not being honoured.
By the way I am running on Windows 10 Pro (10.0.15063) if that is relevant?
So still no progress...