• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

FM11 hanging/crashing with FrameScript 5

Community Beginner ,
Feb 11, 2014 Feb 11, 2014

Copy link to clipboard

Copied

Hi

My setup: FM11; Framescript 5.2 (5.2R1p251); Windows 7

FM11 is working fine ... but when l use FrameScript, the script runs OK until the end, then FM hangs for ages.

Eventually the FM file reopens but cannot be saved, scrolled .... and sometimes even shows only blank pages!!

Above applies to a file in a book, or a standalone file.

Tried an uninstall/reinstall of FrameScript but problem persists 😞

Anyone know a solution/workaround?

Would really appreciate any help!!

Mervyn

[Thread moved to FrameMaker Scripting Forum by moderator]

TOPICS
Scripting

Views

699

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Beginner , Feb 14, 2014 Feb 14, 2014

Thanks to all who replied to my question.

And to Rick Quatro for the prompt diagnosis!

I have been using the same script since 2005 (to produce linked callouts in a Parts Catalog).

Although nothing has changed in the script itself, the issue is apparently the behavior of FM11 in handling document display commands - which now necessitates changes the script (actually, a set of them).

Rick writes: They changed these commands to be "stack-based" so that somehow they accumulate and cause problems.

If ot

...

Votes

Translate

Translate
Enthusiast ,
Feb 11, 2014 Feb 11, 2014

Copy link to clipboard

Copied

What did the FrameScript people tell you when you contacted them? They're

usually very good on customer support and possible bugs?

Art Campbell

art.campbell@gmail.com

"... In my opinion, there's nothing in this world beats a '52 Vincent and

a redheaded girl." -- Richard Thompson

No disclaimers apply.

DoD 358

I support www.TheGrotonLine.com, hyperlocal news for Groton MA.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 11, 2014 Feb 11, 2014

Copy link to clipboard

Copied

Art, thanks for your reply.

I requested FrameScript support only today - so probably, too soon to expect a reply.

Thought folks on the Adobe forum may be having a similar problem .... and their answers usually very helpful,

Will keep everyone posted.

Mervyn

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Feb 11, 2014 Feb 11, 2014

Copy link to clipboard

Copied

Hi Mervyn, The problem is likely with your script, not FrameScript itself. Have you had trouble with the same script before? What does the script do?

Also, when you get a blank screen like this, you can do this:

1) Choose FrameScript > Script Window.

2) Type this in the Script Window:

Set Displaying = 1;

3) Press the Run button (the last one on the right).

I will be glad to take a look at the script for you. If it is not too big, you can post the code here. Thanks.

-- Rick

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 12, 2014 Feb 12, 2014

Copy link to clipboard

Copied

Hi Rick

Thanks for your reply.

I also received a quick response from the Elmsoft FrameScript support guys.

As you suspect, they too think the problem is with the script itself.

The script I am using was written a long time ago. Up until now it has been working fine (nothing has changed).

Since it's too large to post on this forum, I'll contact you directly.

Thanks in advance for your assistance - will really appreciate help.

Mervyn

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Feb 12, 2014 Feb 12, 2014

Copy link to clipboard

Copied

I have the same setup: Win 7, Frame 11, and  Framescript 5.2 R1 and have no problem running my scripts. I suspect it is something in your script. Have you used these scripts before? If so, what has changed?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Feb 14, 2014 Feb 14, 2014

Copy link to clipboard

Copied

LATEST

Thanks to all who replied to my question.

And to Rick Quatro for the prompt diagnosis!

I have been using the same script since 2005 (to produce linked callouts in a Parts Catalog).

Although nothing has changed in the script itself, the issue is apparently the behavior of FM11 in handling document display commands - which now necessitates changes the script (actually, a set of them).

Rick writes: They changed these commands to be "stack-based" so that somehow they accumulate and cause problems.

If other folks having this problem, hope this helps you too!

Mervyn

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines