Re: problem with nextStyle.name

Article View: adobe.scripting.indesign

Article #8747

Back to adobe.scripting.indesign Previous Next

#8747

From: Dave_Saunders
Date: Thu, 28 Sep 2006 12:02

5 lines
1307 bytes

That would be one way to go. I just suggested to the scripting gurus that returning undefined would be better than the error message, but that might be something that suits a JavaScript user more than the other languages.

When you consider the range of the object model, that the occasional property doesn't always behave the way we want it to is the price we pay for having access to all this stuff. I set the bar quite low when it comes to my satisfaction for these things. For me, the key thing is that InDesign should not crash. Lately, I've had a spate of jobs where crashing has been the norm.

Dave

Technical Details

Message-ID: <3bc1cef3.7@webcrossing.la2eafNXanI>

Path:

arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeed.freenet.de!news.albasani.net!news.isoc.lu!webcrossing

References: <3bc1cef3.-1@webcrossing.la2eafNXanI>

Show Full Headers

Complete Article Headers

X-Google-Thread: f939a,2f8a9309c8ea275e
X-Google-Attributes: gidf939a,public
X-Google-Language: ENGLISH,ASCII-7-bit
From: Dave_Saunders@adobeforums.com
Path: arc1-ca.pugleaf.net!g2news2.google.com!news3.google.com!border1.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!newspeer1.nwr.nac.net!newsfeed.freenet.de!news.albasani.net!news.isoc.lu!webcrossing
Newsgroups: adobe.scripting.indesign
Subject: Re: problem with nextStyle.name
Message-ID: <3bc1cef3.7@webcrossing.la2eafNXanI>
Date: Thu, 28 Sep 2006 05:02:58 -0700
References: <3bc1cef3.-1@webcrossing.la2eafNXanI>
Lines: 13
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message