Adobe support looked into their source code to look for an explanation why nothing happened when using the fitting option in question (they could repeat the same behaviour), and I got the answer above. So I'm sorry, I don't know whether it has ever been a relevant option to use. But at least I got it confirmed that it's nothing that one should use today. ... View more

I've tested this in InDesign CC 2017 (ver. 12.0.0.81) on Windows, and I get the same behaviour in CS6 for Windows. With your approach we've now got two work-arounds : ) Either explicitly applying the "fittingOnEmptyFrame" setting, or emptying the frame before placing the new image. But I still wonder how APPLY_FRAME_FITTING_OPTIONS is supposed to work. Thanks, Andreas ... View more

Pav55: You made the answer to KinglePandP who seemed happy with the suggestion (8 months ago) to remove the #target directive. Perhaps your answer was meant for me... but anyway #targetengine "InDesign" would not select InDesign as target application for a script in the ExtendScript Toolkit (ESTK). It would just try to create an engine by the name of "InDesign", which would not be good, since I'm running my script in another named engine. When starting a script in the ESTK it has been comfortable to have it select application (InDesign) automatically, and it has worked for me, until the last update. Either it was the update, or it has to do with me having a new login (user) on my computer, I'm not a 100% certain which came first. ... View more

I got the same problem when updating to CC2017. Until then I've been using ExtendScript Toolkit CC with InDesign CC 2015 (and other versions before that) and I've got the #target "InDesign" directive first in my script since many years back. After the update to InDesign CC 2017, ExtendScript Toolkit CC ver 4.0.0.1 does not regard the selection I make in its dropdown (I select "Adobe InDesign CC 2017 (32 bit)(12.032), but I changes the selection to InDesign CS6, and shows this message when I run my code from within the ESTK: Target Adobe InDesign CS6 (8.0) is not running. Do you want to launch Adobe InDesign CS6 (8.0)? Removing the #target directive makes Extendscript Toolkit accept the selected application version. ... View more

We've got a very similar problem. Under certain circumstances, referring to the associatedXMLElements of the paragraph of an XMLElement, only resulted in the associatedXMLElements of the parent story. Something like this... myElem.paragraphs.associatedXMLElements myElem being an XMLElement like "test1" in the sample below: <container> <tech><test1/><test2/></tech> <container> The circumstances when this problem was found: The parent tag "<tech>" was on the same row (same paragraph) as the elements (test1 and test2) we were trying to find. Adding a line break (new paragraph) after the initial <tech> tag and before the ending one, makes the problem go away, but we can't have breaks there. We made a workaround by going via the "words" collection of the paragraph instead, and found all relevant associatedXMLElements that way, but it seems there is a bug in InDesign. // Andreas ... View more

I know this is an old question that has an accepted answer, but still – as I found this thread when looking for a similar thing – I'd like to add that there is a way to move around groups. If you use changeGrep instead of findGrep, you can address the groups using $1, $2 etc, just as in the Find/Change dialogue. The following illustrates in a simplified way how to switch the order of groups 1 and 2. app.findGrepPreferences.findWhat = '(abc)(def)'; app.changeGrepPreferences.changeTo = '$2$1' myDocument.changeGrep(reverseOrder) I'm aware that this is somewhat beside the point since you explicitly asked about putting the groups in a variable – which you might need, and also this way won't let you move the groups outside the context in which they were found. But at least this is a way to manipulate the location of groups. ... View more

I would still like a more detailed answer from Adobe. Including an answer to why it's an "expected behaviour" and not a bug. I didn't expect it to behave like that – one way on Mac and another way on Windows. ... View more

I'm trying to get in touch with people at Adobe to get the answer verified. Seems like a very odd decision to do. Of course the <SELECT> behaviour on Mac is expected if you know about it, as I guess the employee at Adobe did. But even so, the answer he gave ... is odd. It's too short and unhelpful. ... View more

I found a disappointing answer to the same question, at the Extension Builder Forum. "This is expected behaviour", an Adobe Employee wrote (HTML &lt;select&gt; options are cut off). ... View more

I've got an Extension Builder prerelease login, but as I understand it, that forum is just about the Extension Builder software – the development tool. Not about CEP technology as such(?) I'm trying to open a support case now that I know that it's no mistake from my side, since you got the same problem. Thank you for testing! ... View more

I removed almest everything else from the HTML file, so that no styles should be able to affect the dropdown box, but still it is limited by its containing window in InDesign. Am I the only one with this problem? Here is the HTML file I tried with last, if someone would like to give it a try as an Extension on their mac: <!DOCTYPE html> <html> <head>     <title>Dropdown test SELECT on Mac</title>    </head> <body>     <select>         <option>Selection 1</option>         <option>Selection 2</option>         <option>Selection 3</option>         <option>Selection 4</option>         <option>Selection 5</option>         <option>Selection 6</option>         <option>Selection 7</option>         <option>Selection 8</option>         <option>Selection 9</option>         <option>Selection 1</option>         <option>Selection 2</option>         <option>Selection 3</option>         <option>Selection 4</option>         <option>Selection 5</option>         <option>Selection 6</option>         <option>Selection 7</option>         <option>Selection 8</option>         <option>Selection 9</option>         <option>Selection 1</option>         <option>Selection 2</option>         <option>Selection 3</option>         <option>Selection 4</option>         <option>Selection 5</option>         <option>Selection 6</option>         <option>Selection 7</option>         <option>Selection 8</option>         <option>Selection 9</option>         <option>Selection 1 ASDF</option>         <option>Selection 2</option>         <option>Selection 3</option>         <option>Selection 4</option>         <option>Selection 5</option>         <option>Selection 6</option>         <option>Selection 7</option>         <option>Selection 8</option>         <option>Selection 9</option>         <option>Selection 1</option>         <option>Selection 2</option>         <option>Selection 3</option>         <option>Selection 4</option>         <option>Selection 5</option>         <option>Selection 6</option>         <option>Selection 7</option>         <option>Selection 8</option>         <option>Selection 9</option>     </select> </body> </html> ... View more

This is the same CEP interface but run direclty in Chrome on the same Mac as the one in my original question. As you can see, the dropdown is not limited by the outer window borders of Chrome. That only happens inside InDesign on Mac. ... View more

Yes, it worked! The user with the I/O and CSXSEvent errors has tested the new version, and the errors were gone! Thanks again! ... View more

I agree with you completely Maka, and there are lots of questions about finding ones old posts, so your question is very relevant. I'm looking for a list of my own posts. You should not have to bookmark everything you write on a forum, or every thread that you follow and would like to find your way back to now and then. This seems to be a missing feature on this forum platform. Edit: Now I found what I was looking for: 1. Press the small avatar in the upper right. 2. Press the large silhouette 3. Press Contents 4. Press Following A list of the threads that you are following will show. And to find your bookmarked pages on this forum, you press the "More" menu to the right of Contents, and select Bookmarks. Swedish text on the screen shots, sorry about that, but I guess you will be able to locate the links anyway. Edit 2: To get to your bookmarked thread on the forum, there is a quicker way: just put the cursor in the search field in the top right corner, and select "Bookmarked" in the dropdown list that will show. There is also a couple of "Recent" lists that show the threads that you have visited many times / most recently. Andreas ... View more

Thanks! If this change makes the I/O or CXSXEvent errors on Mac go away, I'll be sure to mark your answers as correct! But it'll be a few days until we can test it. I'll write again then. ... View more

Wow... I never noticed any news about it being added as an embedded resource to InDesign! (I just thought that Loic had left out the path in the sample code, or that it was from some generic example, since some of the other applications has had it builtin for some time.) Was there an announcement from Adobe that I missed? Anyway it seems to work..! 🙂 At least my own Windows computer. I'll make a new version and ask the one of the Mac users to try it out as well. Would you happen to know why there is a backslash in some online code samples? As in the second line below: var externalLibrary = new ExternalObject("lib:PlugPlugExternalObject"); var externalLibrary = new ExternalObject("lib:\PlugPlugExternalObject"); ... View more

I found a few threads about I/O errors and ExternalObject: https://forums.adobe.com/thread/1444959?tstart=0 reads: " it turned out to be OSX Deployment Target setting under Build Settings > Deployment of the target.  I had to switch to OS X 10.8 for it to work." https://forums.adobe.com/thread/1445754?tstart=0 reads: "I got it, the framework is for 32 bit not 64 bit" https://forums.adobe.com/thread/1245938?start=0&tstart=0 reads: "In Windows 64, if your application is compiled 64bit then you can only access InDesign 64bit and its object library. However if your app is 32 bit then you can only access InDesign 32bit and its object library." But could 32/64 bit differences be an issue using HTML5/JS/CEP? ... View more

The code above was from the js file. I will have to go on and find out what line in the jsx file it is that the error is taking place. But it will probably be after the holidays (just to remind myself) : //Load the PlugPlugExternalObject library. We use this external object to pass //events back to the user interface of the extension. //The file path is passed to this function from the JS/HTML side of the extension. function loadPlugPlugLibrary(filePath){     //filePath is escaped, so unescape it before using it.     filePath = unescape(filePath);     try {         var externalLibrary = null;         var plugPlugLibraryFile = File(filePath);         if (plugPlugLibraryFile.exists) {             var externalLibrary = new ExternalObject("lib:"+ plugPlugLibraryFile.fullName);             var data = "PlugPlug library successfully loaded!";             var csxsEvent = createCSXSEvent("plugPlugSuccess", data);             csxsEvent.dispatch();         }         else {             throw new Error("Can't find PlugPlugExternalObject: " + plugPlugLibraryFile.fullName + " File: " + $.fileName + " Line: " + $.line);         }     }     catch(error){         alert(error);     }    } ... View more

Yes, you are right. It seems to be a formatting thing. I checked the results text file where I had saved the output from the mac alert box, and there it says /Library/Application%20Support/Adobe/CEP/extensions/cc.idp/jsx/libraries/PlugPlugExternalObject-Mac/osx10_64/PlugPlugExternalObject.framework (without the space that was in my message above.) But thanks, for noticing! ... View more

Some first-hand experience on Max OSX now. I've seen the I/O error so far, but not yet the CSXSEvent error (it might be I need some more parts in order on the Mac that I'm testing on to get to that, don't know yet). I'm using the code below to load the PlugPlug library, I believe I got it from Olav Kverns introduction (Change as a Way of Life: CC Extensions and the Third-Party InDesign Developer). //This function takes care of loading the PlugPlugExternalLibrary object on //the ExtendScript side. We'll use this object to send InDesign event notifications //and data back to the JS side of the extension. function loadPlugPlugLibrary(){         var csInterface = new CSInterface();     //Determine the plaform, so that we can direct our ExtendScript to the correct version.     var osInformation = csInterface.getOSInformation();     // alert(osInformation);     var plugPlugFile;     if(osInformation.match(/Mac OS/gi)!== null){         plugPlugFile = csInterface.getSystemPath(SystemPath.EXTENSION) + "/jsx/libraries/PlugPlugExternalObject-Mac/osx10_64/PlugPlugExternalObject.framework";     // alert(plugPlugFile);     }     else{         if(osInformation.match(/64-bit/gi) !== null){             plugPlugFile = csInterface.getSystemPath(SystemPath.EXTENSION) + "/jsx/libraries/PlugPlugExternalObject-Win/win64/PlugPlugExternalObject.dll";                }         else{             plugPlugFile = csInterface.getSystemPath(SystemPath.EXTENSION) + "/jsx/libraries/PlugPlugExternalObject-Win/win32/PlugPlugExternalObject.dll";                            }     }     plugPlugFile = escape(plugPlugFile);     alert(plugPlugFile);     csInterface.evalScript('loadPlugPlugLibrary("' + plugPlugFile + '")');     alert('2'); } At line 24 the alert-box shows this path: /Library/Application%20Support/Adobe/CEP/extensions/cc.idp/jsx/libraries/PlugPlugExternalObject-Mac/osx10_64/PlugPlugExternalObject.framework ... and by right-clicking in the alert-box I can select to show that file path in the Finder. Doing so, the Finder shows up at this path. Seems ok to me. But then the I/O error message is shown (between line 24 and line 26). I temporarily went into system settings and allowed all programs to be trusted, not only the ones downloaded from "Store" etc... and restarted InDesign and the Extension, but I got the exact same error. I don't know what to make out of it. Thanks, Andreas ... View more

In my initial question I wrote that the first one of our users who experienced this error "had not checked the "Don't show again" checkbox" when the error went away. It turns out that this was not necessarily true, since I found another mail where it seems he did uncheck that very checkbox, but I'm not quite sure whether that was an earlier installation. ... View more

The update with the newest CSInterface file was put on place (manually) today. The CSXSEvent error is still there on Mac, and so is the "I/O error". The errors are not present on Windows, and the interface seems to work on Mac, but with these warnings showing up. ... View more

Yes, the CSEvent function above exists in the CSInterface library and looks fine. I've updated the add-on with the latest CSInterface file, but due to installation problems, add-ons are not installed or automatically updated at the users computers, so I don't know the result yet. Users don't get the update. According to this post Re: CC2015 Extensions gone the issue with extensions not appearing in InDesign should have been resolved in a "Creative Cloud desktop app" update, but I'm not certain whether Adobe means that you should still – after six months – have to download a specific version of the CC desktop app manually. I'm positive that there have been automatic updates after that was written, and I guess that the link in that post by Monica Singh is leading to the latest version of the CCDesktopApp: https://creative.adobe.com/products/download/creative-cloud so I don't know what to make out of it. Monica Singh wrote that "it is not an auto update hence you are required to download the patch and then install manually." The persons responsible for installations at the company where the extension is installed, say that the synchronization does not work, no matter what version of Creative Cloud Desktop App they install, but they are investigating further. I'll keep you posted. Thanks, Andreas ... View more

I am loading the PlugPlug library, and so far I've never seen these errors on Windows, but users on Mac are reporting them. Looking through the resource files for the code, I should probably update my CSInterface.js file, from this link, since my version is 5.2, and there are versions >6 now. https://github.com/Adobe-CEP/CEP-Resources/tree/master/CEP_6.x There seem to be no new versions of PlugPlugExternalObject since 2014: https://github.com/Adobe-CEP/CEP-Resources/releases/tag/1 ... View more

I agree with Luca Bisin. I saved a document as "Chépitre 01.indd" and ran your script. This was the result: What version of InDesign do you have? This was CC 2015.2 (latest CC version). Perhaps there might be another ASCII / UTF8 representation of the letter "é" in the filename, than the letter é that we are testing with. Andreas ... View more