Basically, you send a string of the code you want to run to Ai via BridgTalk and it gets executed as it happened from within your script. Yeah, I have only experimented with palettes and BridgeTalk a little bit because it's messy but here is a script I wrote the other day to answer a question on this forum about clicking buttons in a palette. My pretty buttons are useless again except on whatever layer or objects I happen to have selected when I run the script - which defeats the purpose of using a window, since I might as well be executing a one-off script to do the same operation.Īm I crazy or doing something incorrectly? Or is Illustrator's implementation of ScriptUI really just this borked?
If I simply change "palette" to "window", my script has access again to the document - but now Illustrator's interface is locked until I close the script window. If I create a "palette" window, basic user functions in Illustrator work (selecting objects, navigating, etc.), but the palette window script has no access at all to the active document, so all my pretty buttons in the script window that do the awesome things are useless.
But something seems to be broken in Illustrator's implementation of ScriptUI. In After Effects, I can create a dockable dialog with access to the whole project. Coming from a familiarity with scripting panels in After Effects, I'm really confused about how to accomplish the same tasks in Illustrator.
0 kommentar(er)
