ScriptUI Forums

Breakpoints in the ESTK?

2011-10-11T07:32:55Z

I can answer my own question: You just have to start the script from InDesign first. Then you can close it, and debugging will work as normal from the ESTK.

Background color for edittext changes window colour

2011-10-01T05:20:41Z

Yes it's an error. It will be fixed in future versions.

Treeview events, and storing object keys in nodes (objects)

2011-06-27T02:53:19Z

Window1.chapterTree.tvwTree.onExpand = function (item){ var strXML = getGroupsByParent(item.key); // Get the XML tree here, as a string, based on the ("user-defined") key property of the item clicked. // Make an XML object out of the string. var myXML = XML(strXML); for (var i=0; i < myXML.children().length(); i++){ // "node" creates an expandable node var aNode = item.add("node", myXML.chapter); aNode.text = myXML.chapter.@chapter_name; aNode.key = myXML.chapter.@chapter_id; // ("item" instead of "node" creates a non expandable node (no plus-sign)) } } The fine thing with the code above is that the id of the node, the "chapter_id", can be stored as a generic key, and you can get hold of that key in the expand event, later on.

How do you get ScriptUI windows to stay open?

2011-06-23T10:40:48Z

I found a splendid explanation on the Adobe InDesign forum: "If I am correct you must first execute the script from the scripts panel so the session for the targetengine is set. I ran into this problem when first trying to run the script from estk. But usually corrects itself once you run it first from scripts panel. 1. Open script in ESTK. (Make sure its linked to application). 2. From Scripts panel (in InDesign) execute script. 3. Try running script from ESTK 4. You should see the targetengine changes to session instead of main." This works. Sometimes breakpoints don't get hit, but a few tries... and they do... (still not sure what makes them work).

Debugging in the ESTK

2011-06-23T09:58:14Z

Hi! Is there a good explanation how to get debugging to work along with ScriptUI, using the ExtendScript ToolKit? Sometimes debugging works fine, but on other times not at all. I suspect the targetengine might play some role in this? Sometimes, pressing F5, break-points don't seem to get hit, but the same code may very well be working when starting the program with F11... letting the window be declared while stepping over the lines and then pressing F5. Best regards, Andreas (I mistakenly put this question in the Rapid Script UI part of the forum, sorry, feel free to remove that, Steven!)

Great tool for building user interface from scratch

2011-06-15T08:07:08Z

Thanks for your compliments. You should be able to have immediate preview, even without F5.

New Features 1.1.0.8

2011-06-15T08:04:42Z

I must apologize. There is an error in the create events option for the window, where when true (the default) events are not created. It should be the opposite. For now set it to false, and events will be created. The option to turn it off, is to be used together with including file at the end of the script for your implemented events which will be used instead of the generated events. If I get a chance II will fix the error, though I am quite swamped.

MeasurementEditboxes missing?

2011-06-15T08:00:07Z

It may be possible with hack, but not built in to InDesign as you said.

CS5 support

2011-06-14T06:39:59Z

I suggest adding support in Rapid ScriptUI for CS5 (and 5.5). Best regards, Andreas

guides not offsetting properly

2011-01-10T03:15:44Z

Ah sorry bout that it is photoshop CS5