Article View: adobe.scripting.indesign
Article #15118Re: JS: Unsuccessful Search Response
From: Dave_Saunders
Date: Tue, 30 Dec 2003 13:36
Date: Tue, 30 Dec 2003 13:36
3 lines
890 bytes
890 bytes
Aha! Clearly the coffee is working slowly this morning. The thing is that with that particular return, myFinds.length is zero, so you don't have to worry about anything other than the length of the result to know whether or not anything was found. Dave
Technical Details
Message-ID:
<2ccf2002.0@webx.la2eafNXanI>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!fu-berlin.de!newsfeed01.sul.t-online.de!t-online.de!webxReferences:
<2ccf2002.-1@webx.la2eafNXanI>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f939a,76fff1fa9bbb0ed,start X-Google-Attributes: gidf939a,public X-Google-ArrivalTime: 2003-12-30 05:37:36 PST From: Dave_Saunders@adobeforums.com Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!fu-berlin.de!newsfeed01.sul.t-online.de!t-online.de!webx Newsgroups: adobe.scripting.indesign Subject: Re: JS: Unsuccessful Search Response Message-ID: <2ccf2002.0@webx.la2eafNXanI> Date: Tue, 30 Dec 2003 05:36:07 -0800 References: <2ccf2002.-1@webx.la2eafNXanI> Lines: 6 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit