Explore related tutorials & articles
31
Replies
Best you can do is in action flyout use Insert menu Item and type "Other scr" then click find it will fill in the rest and update to Title Case, so you know you got the right command.
You may wish to move your scripts to this folder on windows, similar on mac
C:\Program Files\Adobe\Adobe Illustrator 2021\Scripting
restart illustrator, and they will show up under File >> Scripts. If you have many scripts you can use folders to group them by category.
If you are looking for a simple, easy-to-use and straightforward Scripts palette, I can recommend two that are very similar to each other. One is called "ScripshonTrees" and the other is called "Scripts Panel". Both can be simply installed via Creative Cloud Plugin administration and do also work in Photoshop ("ScripshonTrees" also in InDesign).
"ScripshonTrees" has a nice search function that may be very useful if you have many scripts inside nested folders.
Probably the most sophisticated Scripts palette out there at the moment is called "LAScripts", provided by Alexander Ladygin. It comes with an additional Toolbar palette that may be useful sometimes.
"LAScripts" is more than just a script executor. It also has a pretty good source code editor to modify scripts on the fly and some other useful things. It works in Illustrator, InDesign and Photoshop.
Unfortunately, at the moment it is a bit tricky to install "LAScripts". Theoretically, it can simply be installed in your Creative Cloud Plugin administration, but this way the installation won't work properly and only shows an empty palette most of the time. You have to install it manually with some additional adjustments. Then it works well.
I haven't tried Silly-V's approach so far, but will do it certainly. Thanks for sharing, Silly-V.
I believe you just single-click those buttons and it should work.
But, these scripts may have to written in a certain way.
It should work with all ways though, but maybe something in my latest changes makes it only work with this type of script:
//@target illustrator
function test_1 () {
alert("Hello World!");
}
test_1();
I haven't tested it with a script that isn't wrapped in a function like so, maybe that's the issue.
Edit: I apparently have done some more changes to it and just pushed them up. Not sure if it would make it better or worse though. But it still does work on 'my machine', so you should also see a result like this:
Update: the script has been fixed up and edited to get a sense if we have a case of 'bad Mac File props' to go a different path and use a method such as eval("#include 'path/script.jsx'") to launch a script and still be able to provide some arguments to it, because in either case this script panel still writes a dynamic script file to the local temp directory (which I found on my new Mac is to a weird location /var/folders/ch/...).
However, with the Windows working BT-enabled method, we could actually run scripts to different apps from the script panel. With eval script the way I have it, even if adding "#target photoshop" into the top will have no effect; the script still runs in Illustrtor.
The real issue however is the Mac problem with BT, it shows me this:
Even on a basic example. Maybe it's the new M1 computers.
So, my new fix entails this condition in a vital place:
const isUnusableMacFile = (SESSION.os == "Mac" && sf.modified === null);As you see here, the condition states that when the OS is found to be a 'Mac' via my code and the file in question's modified property is a null, then we possibly have a BAD mac that shows null modified-times even when they aren't supposed ot be null. In this case, which I am able to reproduce at will, this fork will make it go eval the file. Still not bad, and we still could potentially get results out of that, thanks to the magic of eval. However, we can't run other apps and we have a potential for some differences in how the scripts may act when called from BT and not from BT. Some differences may take years to spot with a terrible scenario at the worst time in compex edge-cases.
But hey, we can get a decent Hello World out of it now!
Anyways, with the new fix, I think it's still a good tool.
For example, you can arbitrarily nest multiple copies of this panel script along with your other scripts into folders to create pop-out toolboxes. Each one can be named a different name and its settings then will be unique to that tool panel. You can make different tooboxes for all occasions.
AdChoices