: 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.
It is very common that colors are specified as integer literals in code. This is always
done using the hexadecimal literal syntax.
As such, it is very difficult to read colors in decompiled code if the values aren't
expressed in the correct base.
Please add code that identifies obvious colors and reformats their output in the code.
Sometimes decimal is much more readable than hex, so it wouldn't be so good to use always
This is why this task was not implemented by me.
Sometimes a small number can be a color (255 = 0x000000ff), so it is not obvious which
number should be written in hex format.