+ 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.
Yes, that could be useful. One time I needed to change (just for some tests - anyway
result was not so good as I expected :D) "Display rect." and can't do it with FFDec. So I
converted with other program to xml (at that moment FFDec didn't supported this) and
changed this parameter. But for me it has the lowest priority comparing with my other
Ok, but it is not just a new magic number in the code, it is using the same constant,
which was already exist in the code for searching the swf in memory. (SWFSearch.java line
And the combo box is filled dynamically from 1 to this limit. So if you want to eliminate
this limit, and allow version numbers up to 255, it should be modified in SWFSearch too
for the consistency
Ok, now you can edit the compression here.
You can select and save invalid combintaions, too. but a warning message is displayed,
which can be:
- GFX supports only uncompressed or Zlib compressed content.
- Zlib compression needs SWF version 6 or greater.
- LZMA compression needs SWF version 13 or greater.
Is there any other invalid combination?
Is it ok now?