Any changes you make to the manifest will not apply until restart. There is a cache that can effect panels. C:\Users\YOU_USER_NAME\AppData\Local\Adobe\InDesign\Version YOUR_VERSION_NUMBER\YOUR_LANGUAGE\Caches\InDesign SavedData You can delete it if you want to reset it. You should be able to set the title dynamically using csInterface.setWindowTitle('fred');  or window.__adobe_cep__.invokeSync("setWindowTitle", 'fred'); but it's not working on InDesign (BUG) at least on Windows. It did work in InDesign 2015 CEP 6.0.1 but by InDesign 2017 CEP 7 it broke. Oh well! If the issue is really important you can either write the panel on an app were it works like Illustrator or file a bug report and hope it's fixed before CEP is chucked.  ... View more

manifest.xml in the extensions CSXS folder. That said, looking at your question again it looks like you are talking about a native Adobe extension and not something you have developed yourself, the rules for that could be quite different. You should not need to set the debug mode for the native extensions. I would recommend asking the question on the general After Effects forum. After Effects . The the problem was with InDesign I would recommend resetting your preferences would be the first thing to try but I have no clue about AE. ... View more

Did you try <Parameter>--disable-application-cache</Parameter> within your <CEFCommandLine> section? ... View more

1) Do you have? <Lifecycle>     <AutoVisible>true</AutoVisible>     <StartOn>         <Event>applicationActivate</Event>     </StartOn> </Lifecycle> 2) Have you got your .debug working? 3) Do you really thing that support get better with the size of a company! ... View more

A "+" for the unnamed swatches is that they can keep the swatch panel clean for frequently used swatches. Case 1: You have a long document and frequently use 3 swatches but on one page use 50 which you don't plan one using again. Case 2: You have a really lot of 1 off colors, performance will be severely affected because the swatch panel needs to be maintained.  ... View more

It's going to be a lot more efficient than Robert's method if ones scanning a document but you need to add the properties you want to check, which actually is not such a big deal as long as you know how to either copy and paste or sampleTextStyleRange.reflect.properties and then filter out the undesirable ones. That said it would be interesting to see some timings on real life documents and not just 5 line test documents. ... View more

Here's another approach, depends exactly on what you are looking to do. /** * [matchesCharacterProperties]                 matches textStyleRanges with a sample style * @param  {DOM TextStyleRange}                 sampleTextStyleRange    Sample character, textStyleRange * @param  {DOM Collection of TextStyleRange}   textStyleRanges         Collection of ranges that uses .everyItem() or itemByRange() * @param  {Array}                              properties              [Optional defaults to set list] properties you want to match the sample * @return {Array}                                                      Array of matching textStyleRanges * By Trevor http://creative-scripts.com 25 Dec 18 * Not Optimized Uses toSource which will probably be dumped sometime */ function matchesCharacterProperties(sampleTextStyleRange, textStyleRanges, properties) {     if (!properties) {         properties = [             'appliedFont',             'appliedLanguage',             'appliedCharacterStyle',             'fillColor',             'strokeColor',             'baseline',             'underline',             'capitalization'             // etc. etc. etc.....         ];     }     if (typeof properties !== 'object') {         properties = [properties];     }     var n, propertiesCount, sampleProperties, textStyleRangeProperties, textStyleCount, match, c, matches, textStyleRangeArray, propertiesCache;     var resolveProperties = function(properties) {         if (typeof properties !== 'object') {             properties = [properties];         }         return properties.toSource().replace(/^\[/, '').replace(/]$/, '').split(', ');     };     propertiesCount = properties.length;     sampleProperties = [];     propertiesCache = [];     matches = [];     // cache the properties     for (n = 0; n < propertiesCount; n++) {         // resolveProperties returns an array and we only want the values hence the [0]         sampleProperties.push(resolveProperties(sampleTextStyleRange[properties ])[0]);         // For the propertiesCache we want the Array of results for the whole collection         propertiesCache.push(resolveProperties(textStyleRanges[properties ]));     }     textStyleRangeArray = textStyleRanges.getElements();     textStyleCount = textStyleRangeArray.length;     for (c = 0; c < textStyleCount; c++) {         match = true;         for (n = 0; n < propertiesCount; n++) {             textStyleRangeProperties = propertiesCache ;             if (textStyleRangeProperties !== sampleProperties ) {                 match = false;                 break;             }         }         if (match) {             matches.push(textStyleRangeArray );             // matches.push(c); // if you just want the indexes use this line instead of the above one         }     }     sampleTextStyleRange = textStyleRanges = properties =         n = propertiesCount = sampleProperties = propertiesCache =         textStyleRangeProperties = textStyleCount = match =         c = textStyleRangeArray = resolveProperties = null;     return matches; } alert(     matchesCharacterProperties(         app.selection[0] || app.activeDocument.stories[0].characters[0], // The sample range you want to match         app.activeDocument.stories[0].textStyleRanges.everyItem(), // the COLLECTION you want to check         ['appliedFont', 'pointSize', 'fillColor', 'underline'] // [Optional] the properties you want to match     ).toSource() ); ... View more

I think a good idea is to provide a 4 list like done in many sites. Extensions for Visual Studio family of products | Visual Studio Marketplace https://packagecontrol.io/ Popular, Trending, New, Featured. That way there's an exposure to all but it could be quite a lot of work to implement. I think Jonathan Ferman​ is in charge of this. (Hi Jonathan) ... View more

What Manan Joshi​ said is quite possibly correct. Another possibility is the path being used particularly some paths like desktop. Try using .fsName for the path. "/" should work for Windows but you can try "\\" out of desperation. ... View more

Unless you have a good reason you should probably use SUI instead of app dialogs. They are easier to work with. Peter Kahrel has a good guide to them. ScriptUI for dummies | Peter Kahrel There's also a chapter in the tools kit guide. There's a link to the guide in the help menu of the ESTK (if that's still working by you:) ... View more

Looks like it will be a good replacement, glad it had jsxbin export ... View more

There is obviously a problem with the developers signature which the should fix up. Luc Adriaens​ answer needs a bit of filling in. See Setting Cep Debug Mode and Log Level the Easy Way | Creative-Scripts.com On the Mac the default levels are normally cached so if one does the command in Luc's post one can think it didn't work because it generally won't work until a reboot. Mac in Terminal defaults write com.adobe.CSXS.8.plist PlayerDebugMode 1 && killall -u `whoami` cfprefsd Windows in CMD (Command Prompt) reg add HKEY_CURRENT_USER\SOFTWARE\Adobe\CSXS.8 /t REG_SZ /v PlayerDebugMode /d 1 /f Repeat the above lines replacing the 8 with 9. To get it working for the next CC version use 10 and then 11 etc. I when you repeat the command on the Mac you get an error message don't worry about it, the debug mode was set it's just the cache wasn't in place to be killed but all should work. For both Mac and Windows, you must restart the app. I have an extension that sets the debug level CSTK In Adobe App Console and Development Tool | Creative-Scripts.com  but it's a bit of an overkill for this purpose. Basically what happens is that Adobe expects extensions to be signed with a valid digital signature. When it's not the extension will not function. To get around this one can set the debug mode to true (1) and then non-signed extensions will show up. When we set up this forum the FAQ No 1 on the main page Extensions / Add-ons Development  is "Why my extension stopped working and how to set debug mode and logging levels?" which sends to the top link. I guess people are really not seeing the FAQs HTH Trevor ... View more

Yes, that's a very good point about react. ... View more

Hi Uwe Very interesting about InCopy which my understanding was that it's basically InDesign core with a different set of plugins and UI. Hi Ariel Martinho's method I think is the way to go, XML literals E4X had not been supported in mainstream JS environments for years and I can't see it holding out for long in AdobeLand. Using methods like appendChild is going to make porting to the new environments a lot more simple as those methods are much more similar to what is going to be available. You can see what the engineers come up with but it just a matter of time before it breaks again forever even if they do fix it. ... View more

N.b. The regex was a bit careless should not include \x09\x0a\0d ! it try edit it. ... View more

Regarding the validity of these characterless see Valid characters in XML - Wikipedia It could explain why they work in one version and not the other but still it's strange. ... View more

Interesting one var x, charCode; for (charCode = 0; charCode < 10000; charCode++) {     try {         x = <myxml>{String.fromCharCode(charCode)}</myxml>     } catch (e) {         $.writeln(charCode + '\t' + String.fromCharCode(charCode) + '\t' + e);     } } On Illustrator 2019 no problems. On InDesign 2019 ✏ 0 1   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 2   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 3   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 4   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 5   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 6   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 7   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 8   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 11   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 12   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 14   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 15   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 16   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 17   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 18   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 19   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 20   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 21   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 22   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 23   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 24   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 25   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 26   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 27   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 28   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 29   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 30   SyntaxError: XML error in line 1 - Not well-formed (invalid token) 31   SyntaxError: XML error in line 1 - Not well-formed (invalid token) Solution / Workaround ? xmlRegex = /[\x01\x02\x03\x04\x05\x06\x07\x08\x0b\x0c\x0e\x0f\x10\x11\x12\x13\x14\x15\x16\x17\x18\x19\x1a\x1b\x1c\x1d\x1e\x1f]/g; myXMLSafeContents = myContents.replace(xmlRegex, function(r){return '#!@' + r.charCodeAt() + '#!@@';}); ... View more

You can't do that. What you need to depends on the doc setup. typically you will need to fetch all the objects with the grep and then map each object to the spread it is on. Then you only need to compare object on the same spread and that should go quickly ... View more

The null might do something but the delete won't. Vars are flagged that they cannot be deleted only globals or object / array elements can be deleted. It's easier to make a mess than to clean it up! In terms of compiling I would think that a log out should fix it? ... View more

See Re: InDesign CS6 scripts don't work on CC anymore and Re: Scripting Problem with the Default SplitStory.vbs Schript. Windows Scripting Error No. 429, ActiveX-Component cannot… ... View more

app.findGrepPreferences.findWhat = "~a"; ... View more

If your only looking for anchored objects you can find them with a grep and then you'll only have to deal with them. There are post here on finding them. ... View more

Truncating to 27 digits would still be pretty safe with the chances of collision being very low. To truncate you can use '123456789012345678901234567890'.substring(0,27) or '123456789012345678901234567890'.slice(0,27) ... View more

I might as well make a plug for my GitHub - Trevor-/CSTK: Adobe HTML extension Console for js, jsx and shell and extensions development help and the easier to use GitHub - Trevor-/console Can provide a bit of relief and possibly more useful than the original InDesign CS built-in script debugger ... View more

Ehm, maybe I should move it back? ... View more

Moved to JavaScript​ ... View more

Makes one wonder how the bug was created, what is the relationship between : and 10  ? Using base 36 (or 17 up) provides : 10 ; 11 < 12 = 13 > 14 ? 15 @ 16 Looking at the ascii table provides the key ASCII Table | ASCII character codes table 48     30     00110000     0     zero 49     31     00110001     1     one 50     32     00110010     2     two 51     33     00110011     3     three 52     34     00110100     4     four 53     35     00110101     5     five 54     36     00110110     6     six 55     37     00110111     7     seven 56     38     00111000     8     eight 57     39     00111001     9     nine 58     3A     00111010     :     colon 59     3B     00111011     ;     semicolon 60     3C     00111100     <     less than 61     3D     00111101     =     equality sign 62     3E     00111110     >     greater than 63     3F     00111111     ?     question mark 64     40     01000000     @     at sign 65     41     01000001     A 66     42     01000010     B 67     43     01000011     C 68     44     01000100     D 69     45     01000101     E 70     46     01000110     F So now we know! ... View more

And for what app would that be? There's a plugin you can bundle for extensions in Id, Ai and Ps. I'll post a link later. ... View more