+ 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 file
> What is the expected output? What do you see instead?
Project tree collapses to a zero height and needs to be resized again with the mouse so it
would become visible
Fixed. I know that there are a lot of classic intrerface releated problems (it was created
today, and not well tested), please write them to this issue. I'll try to fix them, but it
has lower priority.
JPEXS? what do you think about classic interface? how should it look like?
telling the truth, i created the classing interface only for you, and because it was not a
I don't want to decide how the program should look like, because I'm not very good in
developing/creating UIs (drawing icons, etc). I'm only a (even not Java) programmer, who
hates "drawing" UIs:)
I don't think going back to classic UI is the right future for our decompiler.
Adding a toolbar will lead to something ribbon-like and this is wasting time of
I think it would be better if we had other features improved, like more editation,
assembly, deobfuscation, code navigation and so on.
If you must have classic UI, then all ribbon functionality should be accessible via menu
like in older versions of FFDec. (I think the code for main menu is commented out and is
easy to reimplement)
well, i have plenty of free icons to use and i can create icons if that was needed!
and i think the classic UI looks good as it is, it is just missing a tool-bar nothing
fancy a static toolbar without customize dialog to add/remove buttons is fine, any tool
bar with icons/text will do
JPEXS: the code of the main menu is not commented out since yesterday. It was moved to
MainFrameClassicMenu. It is exaclty the Classic UI:), you can switch to it in advanced
settings. It is working, but some features are missing (which was implemented only in
ribbon, e.g recent files, lot of functions from tools menu) So it was very easy to
"implement", I had to uncomment it only:)
But I agree, the ribbon ui should be improved, the classic ui is only a fallback, if
somebody has problem with the ribbon ui.