Re: linked images in Quark docs
Re: linked images in Quark docs
- Subject: Re: linked images in Quark docs
- From: Hans Haesler <email@hidden>
- Date: Sat, 15 Mar 2003 00:30:29 +0100
On Fri, 14 Mar 2003, Wallace, William wrote:
>
I'd rather not have to close the doc and then reopen it. (...)
All *you* have to do is to run the script and to select an XPress document.
Or, if the document is open, you just run the script which takes care of
closing and opening the document. If you'd like the document to stay
open when the script has finished, then simply modify the last line which
closes the document from 'close document 1 saving yes' to 'save document 1'.
There is absolutely no problem with closing/opening a document. Last
year, I had to update all templates of all of our magazines. And many
documents of the current production. Using the droplet version of the
first script the job has been done very quickly. And safely.
>
(...) If the error you're
>
talking about happens under very specific circumstances, I'd rather check
>
for those circumstances and then abort if there is potential for a problem.
>
What is the threshold at which rotated images cause problems?
One degree. But, as I said, with extreme offset values. And, especially,
when combined with 'Flip Horizontal' and/or 'Flip Vertical' applied. But you
can't check for those circumstances. No way to set up any rules and limits.
Other problems:
- percentages below 10 or greater than 1000 (both can be "achieved"
by using a Resizing XTension).
- a user-modified runaround path throws a message. The user must
click the "No" button (for preserving the runaround). And: before
the script loads the image, it must set the scales to {100, 100}, the
offset to {0, 0} and the angle and the skew to 0. Else the runaround
path will be smaller or bigger than the original one or/and off of the
correct position.
- a contrast can't be re-applied by script.
To speed up the script, the properties are re-applied using a record.
But they are set one after the other. And when an error occurs the
remaining ones are skipped. One must use a try wrapper, else the script
is stopped. To know that an error has occured one can increment a counter.
But it would be better to note the name of the image and add it to a list.
Then you could compare the attributes of the problematic images to the
ones of a copy of the document. Of course it would be even better to
re-apply one property after the other. Then the script could note which
one(s) are not restored. But execution would be slowed down.
All this hassle can be avoided by using the script which I have posted
in my previous reply. Let's XPress do the work... It's easier and safer.
Nevertheless, I'll send you a script or two. I'll have to translate
them, first. But I can't do anything before Monday.
>
Also, how exactly do I reimport the image?
Not you... it's the script which does the job. ;-)
---
Hans Haesler <email@hidden>
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.