🚀 go-pugleaf

While preparing a presentation I'm going to be giving in a couple of months, I took a good hard look at my findPage(theObj) function and I think that this is as good as it gets:

function findPage(theObj) { 
  if (theObj.hasOwnProperty("baseline")) { 
    theObj = theObj.parentTextFrames[0]; 
  } 
while (theObj != null && theObj.constructor != Page) { 
    var whatIsIt = theObj.constructor; 
    switch (whatIsIt) { 
      case null : return null; 
      case Character : theObj = theObj.parentTextFrames[0]; break; 
      case Cell : theObj = theObj.insertionPoints[0].parentTextFrames[0]; break; 
      case Application : return null; 
    } 
    if (theObj == null) return null; 
    theObj = theObj.parent; 
  } 
  return theObj 
} // end findPage 


The previous versions posted in various threads here reflected various degrees of needless caution about what might happen, for example if the object were anchored to text in a cell in an overset table. The above returns null in that case with no need for try/catch.

Notice the use of objects rather than their names. Works! This is similar to the instanceof construction but it's easier to test the negative.

If anyone can knock a hole in the above script, I'd be very interested in hearing about it.

Dave