The only other time I see this happen is if you are running the script from ESTK and the target app is not PS. -X ... View more

Resize the to 1px x 1px with interpolation turned on then check the rgb value of that pixel. It's the simplest thing I can think of so give it a try and let us know how it works out. ... View more

If you still have the orginal SL code, you can use xtools\apps\ActionFileFromSLCode.jsx. ... View more

My bad. You'll need to add #include "/Developer/xtools/xlib/PSConstants.js" after #include "/Developer/xtools/xlib/stdlib.js" That should work. ... View more

cTID is in stdlib.js. getDouble is a method on ActionDescriptor. This is part of PS/JS. There are too possible problems. cTID requires exacty four character. It looks like you're ok here. The other problem is that the 'color' ActionDescriptor may not be and RGB color descriptor. Try this to see what is actually in the descriptor: var keys = Stdlib.getDescriptorKeyNames(color); $.writeln(keys.join(' ')); It will print out the key names in the 'color' descriptor to the ESTK. Place this just above the line that is causing you problems. ... View more

>is there a way or a possibility to add a watermark feature? Write an Action that adds the watermark or write a script that is called by an Action to do what you want. ... View more

Adobe has abandoned tracking ECMA standards. The really bright people behind ESTK and JSX at Adobe have moved on from what I understand. ... View more

In Explorer on Win10, open the properties dialog on the File/Folder and see what it says. Finder may be hiding the files because it's a Mac thing. ... View more

The missing 'include' files may be in the PS C/C++ SDK. ... View more

It's used in ImageProcessorPro (ps-scripts - Browse /Image Processor Pro/v3_2 betas at SourceForge.net). It's actually used twice in the script: once for startup window creation, the other for iteration over the file being processed. The latter is probably of most interest. You don't really need to create a class. It's a function that creates a 'palette' window that I've added stuff to. When you are done with it, just close it. ... View more

Action Manager code will perform better then DOM code in all places. FTFY ... View more

Thanks, Mikaeru, for keeping up the good fight that I could no longer wage. ... View more

Ps. after I finished my code I looked into yours to see differences. But there were 20000 lines! so afer scrolling down and looking for those I needed and still not seeing them I gave up In my app scripts (not lib scripts). Start at the bottom. There is (almost) always a main() function and you can dig into it from there. The most important file is xtools/xlib/stdlib.js (at about 10,000 lines of code).  That's where I started putting useful stuff in the beginning (back in the days of PS7 and no ScriptUI). psx.jsx is a stripped down version of stdlib.js that I used for ImageProcessorPro. It also has a bunch of ZStrings and localization code. ... View more

I have a couple of scripts in xtools that tackle this kind of problem: SLCFix.js // // SLCFix.js // This script does some minor massaging of ScriptListener output // primarily by substituting charIDToTypeID and stringIDToTypeID with // cTID and sTID. In the process of doing this replacement, the // 'var id##' style declarations are removed in the c/sTID calls // placed inline. You'll need to copy the c/sTID definitions from // this file into whatever file you decide to use the converted code. // // One other piece of corrective surgery is to canonicalize all // filename strings to use '/' instead of '\' characters. I didn't bother // messing with the drive names. // // The only thing left that I don't really have a solution for is Actions /// that invoke scripts. For some reason, the return value of the script // is placed in the action and gets output to the ScriptingListener log // file as well. Search for 'jsMs' to see what I mean. Unforunately, in // many case, the return value is effectively the last piece of textual // code parsed, I think. There is not an easy way that I have found to // remove this travesty after the fact, except to do it manually by replacing // the code with an empty string, "". You can, however, remove it before // the fact. Make the last line of your script files 'true;' or, like I do, // the name of the script as a string, e.g. "SLCFix.js"; This has the nice // added benefit of showing up in the debugger console if you are running // the script from within the debugger. // // I've converted up to 20,000 lines of ScriptingListenerJS.log code in one // pass with the only problems being the 'jsMs' garbage. That can, as I said // before, be fixed manually. // !!! This may gave been fixed!!! // // $Id$ // Copyright: (c)2005, xbytor // License: http://www.opensource.org/licenses/bsd-license.php // Contact: xbytor@gmail.com   This handles complete SL log files. There is also an option to use symbolic variables instead of cTID or sTID expressions.   There is also LastLogEntry.jsx which I use more frequently. Do something in PS, run this script, hit the Fix button and you get something that is a lot more readable and smaller. Remember, however, that not all actions in PS are recordable.   // // LastLogEntry.js // Get the last entry from a ScriptingListenerJS.log file. // // $Id$ // Copyright: (c)2005, xbytor // License: http://www.opensource.org/licenses/bsd-license.php // Contact: xbytor@gmail.com //   Both of these 'include' other files (like stdlib.js). I you don't have xtools installed, substitute /xapps/ with /apps/ to get a self contained script. I tend to reuse/include previously written code which is why the /apps/ code is a lot thicker than it needs to be. But, then again, I only need to fix a bug or enhance a feature one place instead of five.   The scripts handle funky file path stuff and a few other odd things and has been used by Adobe for internal research stuff so I have to assume it is fairly stable in addition to be fairly old but continually refined.   It's good to see others do similar  (and more light weight) implementations. ... View more

One of my folders is called "2016 12 09", so I have to escape those characters --> "2016\\ 12\\ 09" I tend to do this instead: app.system('mv -f "/Users/javier/Desktop/Delete/2016 12 09/image.jpg" ~/Desktop');  in code but use escapes on the command line. -X ... View more

Use exiftool and app.system() to call it. Redirect the output to a file and parse the dimensions out of the file. ... View more

When I had to process large batches (10k+) of jpgs, I would run them through IrfanView in batch mode to find the corrupt ones. Using ImageMagick is another reasonable approach to take. ... View more

This is a known problem of all versions of PS. There is nothing you can do in PS/JS to get around the problem. The only solution is to use and external app to recognize the error message pop up and have it select the OK button it displays. I did something like this using AutoHotKey on Windows. There is probably something similar available on OS X. After doing the app.load() call, check to see if the activeDocument is different. This is a problem that Adobe should have fixed a decade ago. ... View more

It looks like line 270 is the culprit. Comment it out like this: //                               alert(message, "Finished", count.error); ... View more

i see i nthe forum some link to ps-scripts Homepage  so i think the adobe forum is not the only efficient way to find information. That site is a PS/JS (retired) developer (me) who hosts xtools, CSX, and Image Processor Pro there.  A better link to work with is https://sourceforge.net/projects/ps-scripts/  then go to Files to get the downloads. I read in the internet a javascript file with this  code ...  var doc = app.documents; .....doc.swatches.length); .....doc.swatches[random_num]; That code was for InDesign JS. PS/JS Document does not have a swatches property in any version of PS. xtools/xlib/ColorSwatches.jsx has code for reading and writing ACO files in PS/JS and fiddling with swatches. All of the bits that you need should be there. ... View more

Here's how I do it in xtools, You can replace f.strf("%e") with whatever function you use to extract a file extension. This expects a Windows-style file selection string and returns that or a filter function if it's on a Mac. isWindows = function() {   return $.os.match(/windows/i); }; Stdlib.createFileSelect = function(str) {   if (isWindows()) {     return str;   }   if (!str.constructor == String) {     return str;   }   var exts = [];   var rex = /\*\.(\*|[\w]+)(.*)/;   var m;   while (m = rex.exec(str)) {     exts.push(m[1].toLowerCase());     str = m[2];   }   function macSelect(f) {     var name = decodeURI(f.absoluteURI).toLowerCase();     var _exts = macSelect.exts;     // alert(name);     while (f.alias) {       try {         f = f.resolve();       } catch (e) {         f = null;       }       if (f == null) {         return false;       }     }     if (f instanceof Folder) {       return true;     }     var fext = f.strf("%e").toLowerCase();     for (var i = 0; i < _exts.length; i++) {       var ext = _exts;       if (ext == '*') {         return true;       }       if (fext == ext) {         return true;              }   }     return false;   }   macSelect.exts = exts;   return macSelect; }; ... View more

s/CVS/CSV/  ? ... View more