B2023-025: In editor, an AER Ro table displays too far to the left so that first column is cut off. This occurs when the table is fairly wide, so that the code was shifting the x location of the table too far to the right. To fix this, if the table’s x location is less than or equal to 0, the x location is reset to 20, thus allowing the left part of table to be visible. If there is step/table in the RNO column, the code was adjusting the y location so that the step/table doesn’t overwrite AER Ro table.
B2023-025: In editor, an AER Ro table displays too far to the left so that first column is cut off. This occurs when the table is fairly wide, so that the code was shifting the x location of the table too far to the right. To fix this, if the table’s x location is less than or equal to 0, the x location is reset to 20, thus allowing the left part of table to be visible. If there is step/table in the RNO column, the code was adjusting the y location so that the step/table doesn’t overwrite AER Ro table.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
B2023-025: In editor, an AER Ro table displays too far to the left so that first column is cut off. This occurs when the table is fairly wide, so that the code was shifting the x location of the table too far to the right. To fix this, if the table’s x location is less than or equal to 0, the x location is reset to 20, thus allowing the left part of table to be visible. If there is step/table in the RNO column, the code was adjusting the y location so that the step/table doesn’t overwrite AER Ro table.
code change looks good.
Tested with no issues using PROMS version 2.2.2404.1808.
A generic release note was added for this update after verifying with JSJ that there should be one. 4/19/24 mrv