With CS5, some things have changed

I just found a difference in the results from allPageItems, in CS5, which I have to code some kind of exception / condition for, in my scripts before upgrading them to CS5:

allPageItems now includes "contained" objects (images and other linked objects, that reside inside rectangles and such) in CS5.

As a simple test, placing an EPS on an empty page in a new document, I run the following code in CS4 and CS5 respectively:

CS5:
app.activeDocument.pages[0].allPageItems
Result: [object Rectangle],[object EPS]

CS4:
app.activeDocument.pages[0].allPageItems
Result: [object Rectangle]

As you can see, we get the container rectangle only, in CS4, while CS5 is returning the object contained as well.

In a larger result set I get the following objects included in the allPageItems in CS5 (not present in the same call in CS4):

[object Image]
[object EPS]
[object Polygon]
[object PDF]

-- Andreas

I cant my progress bar working in CS5, it works if i dont trigger it from the menu.

Does anyone have a working script like this?

Here is the script that i made that adds a menu and when you fire the submenu a progress bar should start working in a window, but nothing is happening except when i add an alert, then it fires.

#targetengine "session"

// Create menu item
var test_menu = app.menus.item('$ID/Main').submenus.add('Test menu');

// Create sub menu action
var test_sub_menu = app.scriptMenuActions.add('Run progressbar');

// Set on invoke action
test_sub_menu.eventListeners.add('onInvoke', function() {
     // Create a simple window
     var win = new Window(
          "window { \
               progressbar: Progressbar { size: [400, 10] } \
          }"
     );

     // Center and show the window
     win.center();
     win.show();
     
     // Set max value for the progressbar
     win.progressbar.maxvalue = 5;
     
     // Make a simple loop from 0 to 4
     for(var i = 0; i < 5; i++) {
          // This should happen every second
          win.progressbar.value = i;
          
          // Sleep for a second
          $.sleep(1000);
     }
     
     // Remove the test menus actions
     app.scriptMenuActions.item('Run progressbar').remove();
     
     // Remove the test menu
     app.menus.item('$ID/Main').submenus.item('Test menu').remove();
});

// Add the sub menu action
test_menu.menuItems.add(test_sub_menu);

Hi everybody,

I'm a vb script developer and I use to access TextFrames with labels, for instance :

set oFrame = myPage.TextFrames.item("bText")

it seems this method no longer exist in CS5... is it a bug ?

Thanks in advance for your answers,

Philippe

I am using a javascript to export a pdf with settings. The script works fine in CS3 and CS4, but not CS5. I get an error from the following line of code for PDF preferences. I am exporting the PDF with OPI. What is the new syntax in CS5 for this setting?

contentToEmbed = PDFContentToEmbed.linkAll;

As pointed out here, there is no longer a property PasteBoardPreferences.minimumSpaceAboveAndBelow.

Use PasteBoardPreference.pasteboardMargins instead.

Harbs

As Jongware points out here, PointType.LINE_TYPE is now PointType.PLAIN.

JPEGExportPreference.resolution became JPEGExportPreference.exportResolution

Footnote will allow the xml tags in CS5?

Arivu..

Some (most) of the text properties which used to return Numbers can now return Strings. This can be a problem if you have a script which adjusts these values.

For example: myText.pointSize = myText.pointSize+1.

In CS4, this would take 12 point text and make it 13 points. In CS5, it'll take the same 12 point text and make it 121 points. This is becase it uses the String "+" operator rather than the Number one. This can catch you really off guard the first time it happens...

The fix is to cast the String as a Number like so: myText.pointSize = Number(myText.pointSize)+1.

Harbs

I'm not so sure that the .parentPage property does away with the need for findPage. I was just working on it right now and came to the conclusion that for a general function, it just changes it a bit:

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

I believe that this function will work with any version of InDesign because it will behave the same as before in versions that don't support the parentPage property.

Of course, if you know you're dealing with an object that has a parentPage property in CS5, you can just go straight for the property.

Dave