: 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.
Since there are new panel in nighly 392 I have some suggestions what can be added there.
First of all it will be useful such a feature to move all text in DefineText left or right
with buttons without editing translatex manually (especially when there are no such a
parameter and I should add it by myself). But if possible it should move text by pixels
because I actually doesn't understand in what values it counts (but I'm sure that not in
plain pixels) so it's hard to calculate needed translatex parameter (even with "Show old
text during text editing" because it usually cuts off) at first time. For example if
1*pixel=100*translatex and if button "move text left" was pressed then translatex =
translatex - 100.
I mean that "auto xmin/xmax" doesn't work with translate buttons. Please test it. Try to
move any text far left or right and you wiil see that xmin/xmax is not changing. Then try
do the same by editing translatex parameter in Parameters window.