Welcome, Guest. Please Login
Rorohiko Workflow Resources
  Welcome the Message Board of Rorohiko Workflow Resources. To register, please e-mail [email protected] - automatic registration has been turned off because of relentless spambots and spammers. This Message Board is not actively monitored. If you have an urgent question, please e-mail [email protected]. If you post it here, it will probably be many weeks before we notice.
  HomeHelpSearchLogin  
 
Page Index Toggle Pages: 1
Send Topic Print
ESTK breakpoints - CS3, APID 1.0.43, win/osx (Read 7075 times)
weller
YaBB Newbies
*
Offline


I Love YaBB 2!

Posts: 10
ESTK breakpoints - CS3, APID 1.0.43, win/osx
02/09/09 at 08:52:03
 
How to stop a script fired via APID and explore it in ESTK?

I tried to insert:

Code:
$.bp(true); 



but it doesn't seem to work. Is there anything else I can do?

Thanks for help
weller
Back to top
 
 
IP Logged
 
Kris Coppieters
YaBB Administrator
*****
Offline



Posts: 181
New Zealand
Gender: male
Re: ESTK breakpoints - CS3, APID 1.0.43, win/osx
Reply #1 - 02/09/09 at 20:16:00
 
Hi Weller,

This does not always work well for reasons unbeknownst to me, but it always works after a few tries with some fiddling in-between, if you know what I mean.

The trick is to use the APIDTemplate, and create a 'compilation document' for your plug-in (set up the proper event list etc... for the proxy frame).

In the resulting InDesign file, click the script proxy frame (to select it) and bring up the Active Page Item Developer palette. Click the 'Use Debugger' checkbox, and then click in the pasteboard area to make it 'take'.

Add 'debugger' statements to your script where you want to break, eg:

...
x = 1;
debugger;
alert(x);
...

Then click the top 'compilation frame' to compile a debug version; alternatively, you can cause the necessary events to occur from the 'compilation document' and get the debugger to kick in. I tend to favour the second approach (i.e. not create an .spln but debug the stuff from the compilation document with some test content added to it).

You can also exercise the debug-.spln file - the debugger should come up. You might need to hit the 'Run' button to make it run through to your debugger; statement.

It's not always easy to make it work, depending on what you're doing - the debugger sometimes pops up an inopportune times.
Back to top
 

Kris
WWW  
IP Logged
 
Page Index Toggle Pages: 1
Send Topic Print