@Jonny – regarding scope of a script, what object it can act upon and what object is "invisible" or not reachable, ExtendScript (and also AppleScript, I think) has not an allTextFrames array.
In contrast to the allGraphics array which returns all Graphic objects, nested or not.
Or the allPageItems array, which returns nearly all page items, and of course also textFrames, which is a subclass of pageItem.
In short and missing some important details: you could loop through all page items of the allPageItems array, check, if one of the pageItems is an overset text frame and do your thing.
In ExtendScript that would be:
var myDoc = app.documents[0];
var textFrameIDArray = new Array();
//Getting the ID of text frames looping through ALL page items:
for(var n=0;n<myDoc.allPageItems.length;n++){
if(myDoc.allPageItems.getElements()[0].constructor.name === "TextFrame"){
textFrameIDArray[textFrameIDArray.length] = myDoc.allPageItems.id;
};
};
//Looping through all Text Frames, also the nested ones:
for(var n=0;n<textFrameIDArray.length;n++){
var myCurrentTextFrame = myDoc.pageItems.itemByID(textFrameIDArray).getElements()[0];
if(myCurrentTextFrame.overflows){
//Some dummy code here
//Sets the fill color of an overset textFrame to yellow.
doSomethingWithOverflow(myCurrentTextFrame);
};
};
function doSomethingWithOverflow(myTextFrame){
//Do YOUR thing here!
myTextFrame.fillColor = "Yellow";
};
Why would I store the ID of an TextFrame in the first loop and not doing instantly something like checking for overflow and correcting that?
Depending what you do with nesting overset text frames, it could be that correcting the overflow could generate new overset text frames and in storing the IDs of all textFrames I can come easily back like in the second loop to check for overset. Sometimes you cannot correct overset so I would not recommend a while loop running on the positive test for overset text frames present in the document.
Uwe
1 Correct answer
14
Replies
I ment guys in the non gender type......but you are correct
AdChoices