Skip to main content
Inspiring
November 20, 2021
Question

vcCode debugger extension issues & how tos?

  • November 20, 2021
  • 2 replies
  • 770 views

Hey

 

Few question to go with ExtendedScript debugger from adobe extension

1. How can I make it stop breaking/crashing ? I used in past adobe toolkit and it never did that. Sadly that tool is no longer developed and vsCode one crashes every 5 mins. Its very difficult to debug a long running process/app if mid way debugging it breaks and crashes. Does any1 have any suggestions?

2. Where can I get autocomplete files, say 

        idMk = charIDToTypeID("Mk  ");
Is just red for me. I need the charIDToTypeID and other adobe functions from somewhere. Any ideas?
3. Any recomendations to improve code writing for adobe products?
 
TIA
This topic has been closed for replies.

2 replies

Legend
November 20, 2021

1. Use alternative ways of debugging - writing logs to the console using $.writeln (), for example.

2. Types for AdobeExtendScript Development Pack
All functions are in the documentation. Nobody forbids you to create your own templates or put functions in variables so that everyone does not type them every time. For example charIDToTypeID many abbreviate to cTT or c2t 

Inspiring
November 20, 2021

1. thank you for the $.writeln ! What is it, How do you know about it? I was always using alert() as I had no idea writeln  exist ! whhh

This helps lots!!

2. Mmm yeah I have it, but half the stuff is missing :- (

 

Thanks for links & info!

Stephen Marsh
Community Expert
Community Expert
December 5, 2021

.toSource() is also useful at times (except for when it returns nothing):

 

alert( myVar.toSource() )

 

More on the Dollar ($) object in the JavaScript Tools Guide PDF or here:

https://extendscript.docsforadobe.dev/extendscript-tools-features/dollar-object.html

 

Inspiring
November 20, 2021

Hey

Yeh I know these parts.

I cant get this one to work

            "targetSpecifier": "photoshop-140.064"

My Ps version is 23.0.1 or something like that, not matte what I type it does not "specify" it properly.

"photoshop-23.0.1"
"photoshop-23.0.1.064"
"photoshop-23.0.1.64"
etc etc.

I keep having to manually re-configure it after each crash ;- ((((

Other stuff I'm aware off, none of which fixes missing members/functions of types/etc that they suggest to use. 

 

 

Legend
November 20, 2021

the #target directive does not have to be specified in the configuration file, it works fine in the body of the script (just as it once did in the ESTK).

 

#target photoshop-160.064
or
#target photoshop