Re: Putting all the elements from one page into another page

Article View: adobe.scripting.indesign

Article #9059

Back to adobe.scripting.indesign Previous Next

#9059

From: Dave_Saunders
Date: Thu, 14 Sep 2006 18:02

15 lines
1492 bytes

Off the top of my head, I wonder if it is the same item -- that's your assumption in the way you've scripted it.

The way you're addressing it is as a reference, and the minute you move that item off the page, the reference is broken.

But how do you get an up-to-date reference to the actual item?

Well, if it is the same item, maybe what you should do is say:

item = sourcePage.pageItems[0].getElements()[0];

that will get you a resolved reference to the item that will survive the move provided that the move does indeed leave the item id intact.

But all this discussion brings into question the need to move the objects on the page afer moving them because you've been moving the wrong objects, if my analysis is correct.

Dave

Technical Details

Message-ID: <3bc17bef.13@webcrossing.la2eafNXanI>

Path:

arc1-ca.pugleaf.net!g2news2.google.com!news4.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.germany.com!news.isoc.lu!webcrossing

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

Show Full Headers

Complete Article Headers

X-Google-Thread: f939a,148c206390c52d9f
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!news4.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.germany.com!news.isoc.lu!webcrossing
Newsgroups: adobe.scripting.indesign
Subject: Re: Putting all the elements from one page into another page
Message-ID: <3bc17bef.13@webcrossing.la2eafNXanI>
Date: Thu, 14 Sep 2006 11:02:21 -0700
References: <3bc17bef.-1@webcrossing.la2eafNXanI>
Lines: 20
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit

Reply to Parent Message