Did you check that the contents changed or if it is the same as before the move?
My hypothesis is the following. When you go to a new segment, a search is done in the glossaries and screen is refreshed. But this operation can be slow, one second is not surprising for me. If in the meantime you used the scroller, once the task is finished the screen is refreshed and moved to the top.
To check this hypothesis, I just published an update 19 where the screen is cleaned in the beginning of the search and filled only once finished. So each time you change segment, there will be a small amount of time (probably 1 second in your case) while the screen contains only the string "Searching...". This version replaces the previous one, so the download link does not change.
In case I am wrong, if you encounter new jumps to the top even when no new searches have been started, then just in case I re-published the previous version here (only the JAR, and only for debug - this will be deleted once we find the solution). Rename the file to OmegaT.jar and replace the existing one in your distribution. Then you are back to update 16, the one before I implemented the configuration using Groovy. Now tell me whenever, in this version, you still have the problem you mentionned. This is for me to know whenever the problem is linked to Groovy or not.
Updates
"after a second the glossar list jumps to top"
Did you check that the contents changed or if it is the same as before the move?
My hypothesis is the following. When you go to a new segment, a search is done in the glossaries and screen is refreshed. But this operation can be slow, one second is not surprising for me. If in the meantime you used the scroller, once the task is finished the screen is refreshed and moved to the top.
To check this hypothesis, I just published an update 19 where the screen is cleaned in the beginning of the search and filled only once finished. So each time you change segment, there will be a small amount of time (probably 1 second in your case) while the screen contains only the string "Searching...". This version replaces the previous one, so the download link does not change.
In case I am wrong, if you encounter new jumps to the top even when no new searches have been started, then just in case I re-published the previous version here (only the JAR, and only for debug - this will be deleted once we find the solution). Rename the file to OmegaT.jar and replace the existing one in your distribution. Then you are back to update 16, the one before I implemented the configuration using Groovy. Now tell me whenever, in this version, you still have the problem you mentionned. This is for me to know whenever the problem is linked to Groovy or not.
Regards
Thomas