-
-
Notifications
You must be signed in to change notification settings - Fork 41
launch.json fields for SWF debugging
When debugging SWF files in Adobe AIR or Flash Player using the ActionScript & MXML extension for Visual Studio Code, a number of special fields may be specified in launch.json.
Custom command line arguments to pass to a desktop Adobe AIR application.
{
"type": "swf",
"request": "launch",
"name": "Launch SWF",
"args": "-custom-arg=hello -another"
}
See AIR application invocation and termination: Capturing command line arguments and flash.events.InvokeEvent
for more details.
The directory where your application's unpackaged native extensions are located.
{
"type": "swf",
"request": "launch",
"name": "Launch SWF",
"profile": "path/to/unpackaged_anes"
}
Unpackaged native extensions are ANE files that have been unzipped for development. Each unpackaged native extension should appear in its own separate subdirectory of the location that you pass to the extdir
field in launch.json.
For more details about unpackaged native extensions, find the documentation for -extdir in Building Adobe AIR Applications: AIR Debug Launcher (ADL).
Note: This field is used for debugging only. When packaging your Adobe AIR application to deploy to devices, use the extdir
field in asconfig.json instead.
The Adobe AIR application profile to simulate.
{
"type": "swf",
"request": "launch",
"name": "Launch SWF",
"profile": "mobileDevice"
}
The following profile
values are supported:
"desktop"
"extendedDesktop"
"mobileDevice"
(Advanced) Custom path to the SWF or HTML file to launch. In many cases, this field can be omitted because it will be populated with the appropriate value automatically.
{
"type": "swf",
"request": "launch",
"name": "Launch SWF",
"program": "bin-debug/MyProject.swf"
}
(Advanced) Path to runtime executable, such as the standalone version of Adobe Flash Player, a web browser, or AIR Debug Launcher. In many cases, this field can be omitted because it will be populated with the appropriate value automatically.
{
"type": "swf",
"request": "launch",
"name": "Launch SWF",
"program": "bin-debug/MyProject.swf"
}
(Advanced) Optional arguments to pass to the runtime executable, such as the standalone version of Adobe Flash Player, a web browser, or AIR Debug Launcher.
{
"type": "swf",
"request": "launch",
"name": "Launch SWF",
"runtimeArgs": "-custom-arg=hello -another"
}
To pass arguments to an Adobe AIR application that you're launching, use args
instead.
The screen density (sometimes called DPI or PPI) of the mobile device to simulate. Customizes the value returned by flash.system.Capabilities.screenDPI
. Typically used in combination with screensize
.
{
"type": "swf",
"request": "launch",
"name": "Launch SWF",
"screenDPI": 326
}
The normal and full-screen dimensions of the simulated mobile device. Typically used in combination with screenDPI
.
{
"type": "swf",
"request": "launch",
"name": "Launch SWF",
"screensize": "480x762:480x800"
}
A number of special screensize
values with predefined resolutions are available, including "iPhone", "iPhoneRetina", and "iPad". See Building Adobe AIR Applications: AIR Debug Launcher (ADL) for a complete list.
The platform string to simulate in the AIR Debug Launcher. Customizes the value returned by flash.system.Capabilities.version
.
{
"type": "swf",
"request": "launch",
"name": "Launch SWF",
"versionPlatform": "IOS"
}
The following versionPlatform
values are supported:
"IOS"
"AND"
"WIN"
"MAC"
- Adobe AIR (Mobile)
- Adobe AIR (Desktop)
- Adobe Flash Player
- Apache Royale
- HTML and JS (no framework)
- Node.js
- Feathers SDK
- Adobe Animate
- Classic Flex SDK
- Library (SWC)
- Royale Library (SWC)