: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means waiting times in the issue tracker are very long and mostly depend on community. Sorry for the inconvenience.
State: new new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
> What steps will reproduce the problem?
Export your SWF's scripts to a folder on your hard drive.
Add new subfolders and script files to the exported folder.
Import all of the scripts (that is, import the containing folder of your "scripts"
> What is the expected output? What do you see instead?
Expected result: All of the script files in the "scripts" folder are imported, including
new subfolders and files; files that are in the SWF but not in the selected "scripts"
folder are removed (optionally after a confirmation prompt).
Actual result: Files in the "script" folder are only imported if their paths and names
match files already in the SWF file. The import feature can apparently be used to edit
scripts already in the SWF, but it cannot be used to add new scripts. The UI doesn't offer
any way to add new subfolders or script files either. This is very, very limiting.
> What version of the product are you using? Is it "nightly build"? Which operating system
do you have?
v10.0.0 nightly 1655, on Windows 10.