A keen VBA amateur scripter I've just started with Extend Script Toolkit for Illustrator CS6 64-bit (16.064). I'm getting a connection with the DLL and basic scripts work however even with small documents (under 1MB) I'm not able to list the document properties under the app object in the data browser (pictured as pending). It takes over a minute and hangs - this is a high-end gaming laptop with 34GB RAM so it's not a hardware issue. I never get to see what's available; obviously I can't code like this.
Does anyone have a fix?
Explore related tutorials & articles
18
Replies
Salut !
Application est l'application Illustrator.
Je ne pense pas que le document ouvert soit en cause ?
Le message d'attente dure une fraction de seconde. (ici Document 4photos_3.ai)
Je n'utilise pratiquement pas extendScript.
CarlosCanto I could make an AI-specific autocomplete extension for Atom if you'd be interested. I have a limited Illustrator-DOM autocomplete for one of my debugging panels already but I'd rather rebuild that one than have others use it as is -- it has a few Windows-specific options (for hotkeys within the editor) so it may not work on mac.
Dalski K, when I first came to these forums and was complaining about ESTK and the JS Scripting Reference because I thought it was hard to get started, Silly-V said something along the lines of this forum and community being "the real documentation". I've found that remark is definitely accurate because I've learned far more with a google search leading to forum posts than I ever have trying to use ESTK's OMV or the Scripting Guide/Reference. I think a critical part of learning is turnover rate, though, and using Atom for scripting instead of ESTK made it far more comfortable for me personally to start. You don't actually need ESTK to write scripts at all, you can do it through Atom using an extension called Process Palette:
I found it through a CreativeCow answer. So I'd argue there's no real advantage to using ESTK over a modern text editor with exception to accessing the console and the OMV (and I'd imagine the Data Browser as well if it weren't broken for me), but seemingly a lot of disadvantages that come with ESTK over modern text editors because it lacks so many features that others have by default -- multi-cursor, third-party apps, robust syntax highlighting, continued support, dynamic keybindings, etc. You can create your own console / IDE as a panel inside AI, even one that runs scripts and code with a hotkey and retains all of ESTK's error warnings:
I mostly use it as a helper function to debug other panels and scripts while writing them within Atom, to bypass the lack of having access to ESTK's console:
I've seen another more robust version of this created by Trevor here. You can also use PlayWrite the same way when writing a completely external script, but you'd need the required function to send a CSXSEvent within the script you're using:
// Rewrites the console line / title
JSXEvent('data here', 'com.playwrite.console')
// Rewrites the editor contents
JSXEvent('data here', 'com.playwrite.rewrite')
// Adds data as next line in editor
JSXEvent('data here', 'com.playwrite.write')
function JSXEvent(payload, eventType) {
try {
var xLib = new ExternalObject("lib:\PlugPlugExternalObject");
} catch (e) {
JSXEvent(e, 'console')
}
if (xLib) {
var eventObj = new CSXSEvent();
eventObj.type = eventType;
eventObj.data = payload;
eventObj.dispatch();
}
return;
}
// ...Or having this in your code allows you to write console.log() and display to this panel as if in normal JS
console.log(someVariable)
var console = {
log : function(data) {JSXEvent(data, 'com.playwrite.console')}
};
CarlosCanto wrote
don't rush about the Atom autocomplete, I'm not in big hurry to get into it.
I'll make a new thread about it.
AdChoices