Re: Problem with compiled script

Article View: adobe.scripting.indesign

Article #18036

Back to adobe.scripting.indesign Previous Next

#18036

From: Dave Saunders
Date: Tue, 06 May 2003 17:56

13 lines
1496 bytes

I think Jay put his finger on it. One of the ways that the scripting system speeds up when run from the palette is to not display changes as you go along (from an external script editor, it tends to catch up between commands, which is one of the reasons it's slower).

You've hit such a case here.

So, what you need to do is force it to slow down before the fit command. Something like:

get character -1 of mySectionTitleLevel2Frame

will probably get the job done (reverting to your original script). What that command does is force the composition engine to step in and compose the frame before releasing control back to the script which should allow your fit command to work.

Fingers crossed!

Dave

Technical Details

Message-ID: <1de8f1c5.7@WebX.la2eafNXanI>

Path:

arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-04!sn-xit-06!sn-xit-08!supernews.com!newsfeeds.sol.net!newsengine.sol.net!hammer.uoregon.edu!logbridge.uoregon.edu!xmission!nntp.infostrada.it!newsfeed01.sul.t-online.de!t-online.de!WebX

References: <1de8f1c5.-1@WebX.la2eafNXanI>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f939a,7f68682032039179
X-Google-Attributes: gidf939a,public
X-Google-ArrivalTime: 2003-05-06 11:08:04 PST
From: "Dave Saunders" <daves@pdsassoc.com>
Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!sn-xit-02!sn-xit-04!sn-xit-06!sn-xit-08!supernews.com!newsfeeds.sol.net!newsengine.sol.net!hammer.uoregon.edu!logbridge.uoregon.edu!xmission!nntp.infostrada.it!newsfeed01.sul.t-online.de!t-online.de!WebX
Newsgroups: adobe.scripting.indesign
Subject: Re: Problem with compiled script
Message-ID: <1de8f1c5.7@WebX.la2eafNXanI>
Date: Tue, 6 May 2003 10:56:00 -0700
References: <1de8f1c5.-1@WebX.la2eafNXanI>
Lines: 20
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message