+ 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?
Using newer versions of asdecbeta1 makes it impossible to change a "public static const"
> What is the expected output?
pushstring "Try to replace this value"
What do you see instead?
m"String" = "Try to replace this value"
> What version of the product are you using? On what operating system?
1.6.7 and asdecbeta1 which is added in the uploaded package.
> Please provide any additional information below. Attach the file you have problem with
if neccessary. If you do not want to publish files YOU CAN CHANGE VISIBILITY TO PRIVATE
Constants are generally initialized in initializers.
Static consts are initialized in class initializer.
Please look in the left bottom panel (Traits list) and click "class initializer" item.
It is regular P-code where these consts are initialized.
I should place some warning in const trait editation panel,
because this is VERY frequently asked question,
few more asking this and I will go crazy!!!
Note to "asdecbeta1": This version probably does not parse class initializer at all.
Is this enough for an answer?
Hmm, I see you attached beta1 too.
It shows class initializer with assignments.
In newer version, assignments to constants in class initializer
are hidden and they are shown directly in const definition,
because if they are in class initializer, they are uncompilable, because you cannot assign
new value to const...
You can access class initializer from traitslist as I stated in my previous post.