![]() 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. |