Skip to main content
Legend
December 11, 2018
Answered

FM2019 - Can't launch the ExtendScript IDE

  • December 11, 2018
  • 2 replies
  • 2536 views

Hi,

FrameMaker 2019, v15.0.1.430, installed with several previous versions.

The File > Script > New Script command does nothing. I can run a script with File > Script > Run. If I launch the IDE with FM2015 and switch the target to FM2019, again I can run a script. Any ideas why I can't launch the toolkit with FM2019?

Thanks,

Russ

This topic has been closed for replies.
Correct answer Stefan Gentz

Hi Russ,

this was a bug. It is fixed by now. Please install Update 2 for FrameMaker 2019.

Cheers,

Stefan

2 replies

rombanks
Inspiring
December 12, 2018

Hi Stefan,

As far as I can see, the availability of update #2 has not been officially announced yet.

I evaluated FM19, with update#1 installed, and it currently is the most buggy version I've seen so far, after FM9.

What does the QA department do?

Inspiring
December 12, 2018

Hi Rombanks,

can't unterstand "FM 2019" is the most Buggy Version. What does this mean for you?

FM 2019 is completely new under the hood, and of course there are Bugs as they exist in any other software too.

But for me 2019 is the best release ever and at least not worse than any version before.

I think you should deliver more details to this statement, so bugs can be fixed. Otherwise Nothing will change

Markus

rombanks
Inspiring
December 12, 2018

Hi Markus,

Apparently, it largely depends on the use case/environment. If you work on some light-weight projects, whether in structured or unstructured mode, FM19 may do the job. This is different in case of large-scale projects including thousands of pages. In my case, FM19 failed where FM15 did what it was supposed to do (slowly but surely) - I am mostly talking about PDF distilling and HTML5 generation. With the trial version of FM19, I couldn't even customize the HTML5 publishing settings - it crashed. I couldn't distill more than 61 pages.
I use FM on Win7. I guess you have already moved to Win10, right?

The product should be tested in different environments and at different stress levels before it is released to the market.

I am sure Adobe has enough resources to fully test the product, without me pinpointing the issues. I've spent enough time working with the Adobe support in the past and showing them the issues I had. Nowadays, I can't allow myself wasting my time on that anymore.

Stefan GentzCorrect answer
Legend
December 12, 2018

Hi Russ,

this was a bug. It is fixed by now. Please install Update 2 for FrameMaker 2019.

Cheers,

Stefan

Russ WardAuthor
Legend
December 12, 2018

Well, how about that. Thanks Stefan.