Skip to main content
B
birnerseff
Inspiring
May 8, 2020
Question

how to debug extendscript of a CEP panel in ESTK

  • May 8, 2020
  • 2 replies
  • 1823 views

`Hi,

 

I have seen a few tips for using VS as a debugging aid for the jsx parts, but are there any instructions on setting up ESTK debugging sessions?

This topic has been closed for replies.

2 replies

M
Community Expert
Manan JoshiCommunity Expert
Community Expert
May 8, 2020

Seems i was not totally correct and things have changed since i last looked at it. Have a look at the following discussion

https://community.adobe.com/t5/exchange/how-to-debug-a-photoshop-cep-extension-with-vscode-extendscript-debugger/td-p/10550627

 

So the idea is to use chrome debugger for the js part of debugging and VScode for the jsx part of debugging. I think there are sufficient instructions in the discussion for you to give it a try.

 

-Manan

-Manan
    B
    birnerseffAuthor
    Inspiring
    May 11, 2020

    Hi,

     

    thanks for pointing me at that discussion; honestly I would have preferred ESTK but it seems to be phased out by Adobe nyways

    M
    Community Expert
    Manan JoshiCommunity Expert
    Community Expert
    May 8, 2020

    I don't think that is possible while the cep extension is being debugged using chrome. What you can do is debug the script standalone using Extendscript or VScode, if there is a problem you can't debug this way and need the whole workflow of Cep extension, then you will have to use alerts, logs messages etc to debug the jsx part of the extension.

     

    -Manan

    -Manan
      M
      Community Expert
      Manan JoshiCommunity Expert
      Community Expert
      May 11, 2020

      ESTK is a 32 bit application and MAC's since Catalina have move to 64 bit only so its just collateral damage that way. Even on systems where you can use ESTK i don't know of any method where you can use ESTK to debug the jsx of a running CEP extension(i may be wrong, happy if someone gives any insight into this). So using ESTK for such debugging is limited to just debugging it standalone, else VSCode is the way to go

       

      -Manan

      -Manan
      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices