BowlerHatLLC / BowlerHatLLC/asconfigc
Issues with building and running animate based projects
- Dominant language
- ActionScript
- Stars
- 21
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
A few little issues with building via Animate:
1. With an asconfig.json that uses an "animateOptions" section, I can successfully build using this method (i.e. where vscode launches animate) but it leaves Animate open, and the fla file is also in a modified state. Very little hope of any kind of tidy automated builds of a whole bunch of fla's this way?
2. Cannot launch the compiled swf to play or debug in vscode. Error is "Error launching SWF debug session ... runtime not found for program xyz.swf". Building a non-animate project in vscode works fine however.
3. vscode flags warnings/errors in the "main" class file that are properties defined for the movieclip inside the fla project. So I can see how vscode can't know about these, but is there a suggested way to suppress these warnings safely?
Contributor guide
Research direction
Start by reproducing the three reported cases using asconfig.json with animateOptions, an Animate project, and the VS Code build/debug workflow. Check whether builds leave Animate or the FLA modified, whether the compiled SWF can launch, and how movie-clip properties are reported in the main class; done means these workflows behave as expected or each limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- build-system, developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100