When you add a new ExtendScript configuration to your launch.json, it will contain only the minimum settings required to start debugging.Ipdb. To start, please follow the standard steps to initialize a launch configuration. Setting up a launch configuration allows you to simplify and customize the process of starting a debug session. Once you have made your choice, simply select your target host application and, if applicable, the target engine and the debug session will start. When you select "ExtendScript", you will be asked to select a Debugging Mode. jsx) is the active file in VS Code, you will be given the option to select "ExtendScript" in the list of debugger options in the dropdown. If you click this button while a file recognized as "JavaScript" (. If you have not yet defined a launch.json file in your project, the Run and Debug view will show the "Run and Debug" button. The ExtendScript Debugger is capable of debugging with and without a standard launch configuration. If your scripts are loaded into an application through a symbolic link (most commonly seen in CEP workflows), the aliasPath configuration property may be required to enable debugging features.CEP environments in particular may benefit from a compound launch configuration to debug both scripting environments simultaneously. Scripts may also be evaluated while an attach debug session is active.This debug session will remain active until explicitly disconnected or stopped. Any breakpoints or uncaught exceptions encountered by the host engine while your attach debug session is active will cause VS Code to show the debug state and enable interacting with the host application. Such a debug session will connect to the specified host engine, inform it that the debugger is active, and then wait for debug messages from the connected engine. To debug ExtendScript triggered by callbacks, start a debug session configured with an attach request type. A launch debug session is only active when the originating script is processed by the host application and will therefore miss debug messages from the host application in these circumstances. with ScriptUI or CEP) requires that the debugger be connected when that script is run. Debugging Event Callbacksĭebugging ExtendScript triggered via a callback (e.g. Once the script evaluation is complete, the debug session will clean itself up and shut down. Any breakpoints or uncaught exceptions will cause VS Code to show the debug state and enable interacting with the host application. Such a debug session will connect to the specified host engine, inform it that the debugger is active, and then trigger the script evaluation. The most direct way to debug a script in the extension is to start a debug session configured with a launch request type. command or by clicking the Eval in Adobe. This functionality may be triggered via the Evaluate Script in Host. The extension supports running (evaluating) a script in a host application without an active debug session. Three common use cases are outlined below to provide guidance on how certain features may be used. This extension was designed to support a wide variety of use cases. It is highly recommended that you read the following section as it provides an overview of how to use this extension with three common use cases. Please see the Advanced Configuration section for a full listing of configuration properties available in V2.Īdditionally, the manner in which the extension operates has changed dramatically. All other V1 properties have been removed and will be ignored. The engineName and debugLevel properties remain unchanged. The following is a table of properties that have been renamed: V1 As a result of this overhaul, the launch configuration properties have changed. The internals received a complete overhaul that substantially increased stability, performance, flexibility, and improved compatibility with native VS Code features. The ExtendScript Debugger V2 is a complete rewrite of the V1 version. The extension requires VS Code v1.62 or newer. Install the extension through the usual means. ¹ Changes to the Caught Exceptions setting while a script is running or stopped at a breakpoint will only apply to scopes created after the setting is changed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |