: 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: 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.
On Windows filenames and paths are not case sensitive. Although I have not seen
non-name-obfuscated swf's that have issues with case sensitivity, when names are
obfuscated there are often name clashes. JPEXs currently does not handle this case when
exporting scripts (files will be overwritten).
Since I believe fixing that problem in a natural way is hard, I propose a new exporting
mechanism, where files will be exported into a zip file (or any case sensitive container
file) which can then either be unpacked and have the names be resolved by the unpacker or,
which is my case, be further processed.
Another simple solution would be some simple XML format that maps QNames to exported files
contents (not file paths, though that might be a possibility aswell). JSon would do aswell
or even a very simple text file with proper escaping.
I would love to do that myself, but I have no expirience with java sadly. If I can help
with defining a file format or anything like that, I would love to.
Thanks for any comments in advance.
Yes, but I decided to put them to the same folder.
So for example if you have the follwoing classes:
the result will be:
My goal was only not to lose any file.
Let me know if you find any problem.
Maybe you are right, and It would be better to have this output:
For me the first solution was much easier and enough.
You can improve it if you want, we will accept push requests.
Ok, I have fixed my tooling to not rely on paths anymore. There seems to be a bug in the
new code though, and I have looked at the commit and cant figure out why, but it seems to
only work for 2 files with the same name, not 3.
In my specific case I have 3 classes, _-e1g, _-E1g and _-E1G, but there are only _-E1G and
_-e1g where _-E1G actually contains the right class and _-e1g actually contains _-E1g.