Article View: adobe.scripting.indesign
Article #8751Re: problem with nextStyle.name
From: Andreas_Jansson
Date: Thu, 28 Sep 2006 13:32
Date: Thu, 28 Sep 2006 13:32
5 lines
1046 bytes
1046 bytes
As long as the behaviour is consequent, that's alright for me. When you are faily new to a language/model (as I am) it's not always perfectly clear what is a bug and what is standard behaviour, and for what objects the same behaviour is supposed to apply. But it comes with time and experience, and frequent reading of this news group. And there always seems to be a workaround (or two), for things to go as you wish. Andreas
Technical Details
Message-ID:
<3bc1cef3.10@webcrossing.la2eafNXanI>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.germany.com!news.mb-net.net!open-news-network.org!news.isoc.lu!webcrossingReferences:
<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: Andreas_Jansson@adobeforums.com Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news.germany.com!news.mb-net.net!open-news-network.org!news.isoc.lu!webcrossing Newsgroups: adobe.scripting.indesign Subject: Re: problem with nextStyle.name Message-ID: <3bc1cef3.10@webcrossing.la2eafNXanI> Date: Thu, 28 Sep 2006 06:32:37 -0700 References: <3bc1cef3.-1@webcrossing.la2eafNXanI> Lines: 9 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit