If you are looking for the decompiler itself, visit https://github.com/jindrapetrik/jpexs-decompiler
NEW : We have got a new blog where we post some interesting SWF internals info.
List of issues#203 editing AS directly shows error when trying to save
Author: 
honfika
honfikaDate created:
Type: bug
Visibility: Everybody
Assigned to:
Labels: AS1/2Direct Editation
State: closed 
> What steps will reproduce the problem?
Open attached swf.
Open frame1/DoAction
Press Edit (experimental)
Press Save
> What is the expected output? What do you see instead?
Current: CURLY_CLOSE expected but DOT found on line 14
Expeced: saving is successful.
> What version of the product are you using? On what operating system?
1.6.4u1
> Please provide any additional information below. Attach the file you have problem with
if neccessary. If you do not want to publish files YOU CAN CHANGE VISIBILITY TO PRIVATE
1.swf (3 KiB)Similar issues in this attached file.
DefineSprite (1): IDENTIFIER or THIS or SUPER expected but LENGTH found on line 8
DefineSprite (2): PARENT_CLOSE expected but FALSE found on line 3
DefineSprite (14): CURLY_CLOSE expected but TRUE found on line 4
DefineSprite (20): COMMA or PARENT_CLOSE expected but MINUS found on line 10
DefineSprite (26): PARENT_CLOSE expected but BRACKET_OPEN found on line 4
DefineSprite (29): CURLY_CLOSE expected but STRING found on line 6
2.swf (70 KiB)
State: new→opened
Version 1.6.6 was released.
Direct editing was totally rewriten,
it should be better now, try it.
State: opened→upgraded
When i try to edit and save the code in the 1.sfw, the saved code will be diffrent.
Here is a small example:
Try to save this:
function plugins(tex)
{
tex=tex.split("\\\"").join("\"");
tex=tex.split("\\\"").join("\"");
}
After saving i got:
function plugins(tex)
{
var tex=tex.split("\\\"").join("\"");
tex=tex.split("\\\"").join("\"");
}
After editing and saving again:
function plugins(tex)
{
var register2=tex.split("\\\"").join("\"");
register2=register2.split("\\\"").join("\"");
}
State: upgraded→returned
State: returned→opened
version 1.6.7 released
it should be better, try it
State: opened→upgraded
Yes, it is much better, I haven't found any problem except issue #264 ("true" statements
in the decompiled code)
I'll test it further, and create a new issue when i find new problems. Thanks.
Checked all reported by honfika bugs in this issue - looks like everything is fine in
1.7.0!
Yes, the previously reported problems was already fixed in 1.6.7. The only problem in
1.6.7 was the "true" statements. You can close this issue, I haven't found any new
problem. I'll create new issue if found new problems.
Okay, thank you for testing this. I want this to be "killer" feature.
It is still marked as Experimental, because Editing is very "risky" and there are surely
some bugs hidden inside.
I am closing this, feel free to create new issues for more bugs...
State: upgraded→closed