If you are looking for the decompiler itself, visit https://github.com/jindrapetrik/jpexs-decompiler
List of issues
: The issue tracker is now writable again and logged users can download files too. But note that our support is very LIMITED.
#562 Editing ActionScript 3 code
Assigned to: JPEXS
Labels: AS3Direct Editation
Title: Editing code?→Editing ActionScript 3 code
Assigned: → JPEXS
Assigned: → JPEXS
Yeah, sorry about that. I meant ActionScript 3. Sorry about the confusion.
You can try newest nightly build. But it is all EXPERIMENTAL and surely contains many bugs.
Well, I tried the nightly build, and while I can say it's functional, it refuses to let me save what I'm editing. Here's the first line of the code I'm trying to edit (which is what the program is complaining about): "package com.giab.games.gcl.ag.ingame" And here's the error it gives me: "DOT expected but IDENTIFIER found on line 1" This keeps me from editing anything, because it's like this on all the scripts in the .swf.
new nightly build released, this should be fixed.
Hmm...now it pretty much crashes (takes forever to attempt to save and never actually does save), and whenever it doesn't crash (i.e. when I'm editing a tiny script), I usually get some sort of error like "CURLY_CLOSED expected but CURLY_OPEN found on line 6", which doesn't make sense since there's MOAR code after the CURLY_OPEN which is mentioned in the error. (something tells me this will end up taking quite a while to get right)
We need the code you have problem with to fix it. Please attach the code here, or better the whole SWF. (Add file button)
I fixed class initializers in newest nightly build so it should be a bit better now. If not, then please attach the problematic code so I can take a look.
Hmm, I found various other bugs now. It's not very useful yet :-(. I will try to improve it and let you know
You can try newest nightly build. It should be better. But I don't think you should trust it much, it's still experimental.
Another fixes in 2.1.0u1, try it.
If any problem occurs, you can create new bugreport. I am closing this issue.