After performing a search retrieving no results ("No matches returned by search.") and using Alt+F (accidentally when trying to use Ctrl+F to return the cursor to the search field), the program stops responding.
I could reproduce the behavior when clicking the Filter button instead, again after performing a search retrieving no results.
I don't reproduce it.
Of course, if I filter on no results, the Editor goes "blank" (there's nothing to display). But if I then hit Remove Filter, everything goes back to normal.
What is your platform and version of Java?
Didier
Thanks for asking, I should have added that essential info, my bad.
I am running Windows 7 SP1 and OmegaT 3.0.8-1 with JRE.
The java -version command gives the following result:
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(Tm) 64-Bit server VM (build 24.45-b08, mixed mode)
Also, after hitting Filter (or Alt-F) the program immediately stops responding. There is no chance to hit Remove Filter.
I don't reproduce it using more or less exactly the same system.
There must be something else.
Didier
I tried again several more times and made some more findings:
Even though the GUI stopped responding, the program kept monitoring changes to the project and writing to the log.
At one try, instead of forcing the program to close I returned focus to the Search window (using Alt+TAB) and could regain control of the GUI (by hitting Esc). In order to go back to normal, I had to simply reload the project.
In subsequent tries, the GUI did not become non-responding anymore, but after hitting "Remove Filter" the Editor pane returned to the first source file in the list instead of the current file.
Attached you will find the log for this session. Fortunately, there are some errors logged. I hope this helps elucidate the issue.
Last edit: Héctor Cartagena 2014-01-17
Thank you for the log. At first glance, I'm not sure the errors reported are related to your issues, but we'll try to check.
Didier
Normally fixed in SVN (/trunk).
It remains to be checked by those who could reproduce the issue.
Didier
Fixed in the released version 3.1.0 of OmegaT.
Didier