🚀 go-pugleaf

I usually switch to spread coordinates to avoid those kinds of issues (although others swear by page coordinates). I use these two functions:

    function saveMeasures(doc, units) { 
      var uPrefs = doc.viewPreferences; 
      var uMeasures = { 
        horiz:uPrefs.horizontalMeasurementUnits, 
        vert:uPrefs.verticalMeasurementUnits, 
        rule:uPrefs.rulerOrigin, 
        zp:doc.zeroPoint 
      } 
      doc.viewPreferences.properties = { 
        horizontalMeasurementUnits:units, 
        verticalMeasurementUnits:units, 
        rulerOrigin:RulerOrigin.spreadOrigin, 
      } 
      doc.zeroPoint = [0,0]; 
      return uMeasures; 
    } 
    function restoreMeasures(doc, measures) { 
      doc.viewPreferences.properties = { 
        horizontalMeasurementUnits:measures.horiz, 
        verticalMeasurementUnits:measures.vert, 
        rulerOrigin:measures.rule 
      } 
      doc.zeroPoint = measures.zp; 
    } 
   


I call these like this--notice the code is inside a function; that makes it possible to use return to exit the script which in turn makes it possible to call the restore function as I exit, using the return in two different places:

  function splitElements(aDoc) { 
    var curPage = app.activeWindow.activePage; 
    var prevPage = aDoc.pages[curPage.documentOffset - 1]; 
    if (prevPage === aDoc.pages[-1]) { 
      alert("Don't run this script on the first page of a document."); 
      return; 
    } 
    var uMeasures = saveMeasures(aDoc, MeasurementUnits.points); 
    var oSized = getOsetElement(prevPage); 
    if (oSized === null) return restoreMeasures(aDoc, uMeasures); // nothing to do 
    splitElement(oSized, prevPage, curPage, aDoc); 
    return restoreMeasures(aDoc, uMeasures); 
  } 


This script needed to convert the measurement units to points because it needs to do calculations involving leading and stroke weights, both of which are provided in points.

Dave