+ update 2020: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means we will NOT develop new features and/or fix most of bugs. We left the tracker running in case somebody from community would like to work on it. Sorry for the inconvenience.
State: closed 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?
Open any swf. Open AS 1/2 (doesn't tested in in AS) script, edit it, save changes.
> What is the expected output? What do you see instead?
Something was changed (according my actions). Nothing was changed.
> What version of the product are you using? Is it "nightly build"? Which operating system
do you have?
latest nightly. Win7&8.1 x64 with latest updates.
> Please provide any additional information below. If the problem is related to a SWF
file, attach it here, otherwise we can't help you.
This bug is quite old. Strange that it still wasn't fixed. After second edit of the script
changes becomes visible.