Features for very long queries

OmegaT's search screens used to be very fast to give an answer, but there is almost one notable exception: the pre-translate screen based on translation memories implies quadratic search (each segment from source against each segment from all translation memories), which can take a while.

Previously, when a query took very long time, the screens seem quite freezed. In DGT-OmegaT 3.0 update 23 we added the following features:

1. During the search, the results pane shows
   • the progress of the search. This is not as powerful as a real progress bar: some kind of searches, such as search in orphan segments, cannot be expressed as percentage (because we cannot know how many orphan entries we have). But almost it shows that the search is not freezed;
   • Total number of results, so that you can stop a search which seems useless;
   • The time elapsed since you pressed the search button
2. A new button "stop" enables to abort and display results (contarily to "close" button, it will display the already found results);
3. You can configure abort of the search not only by number of results, as it was before, but also to define a maximum time for a search
4. in DGT-3.2 update 14: the button "Translate all" can also re-use the result of the search, which makes it faster than if it recalculates what to replace. But don't forget then that if you stop a search, or if it is stopped due to lack of time or max number of results, only found results will be replaced. In such a case we suggest that you always start a new search excluding already translated results.
5. in DGT-3.4-TEST-3 and 3.5-DEV-3.0, if you interrupt the search, not only you see the already found results, but you can restart a new search from the point it was previously interrupted.

The features are implemented globally, so they affect in theory all screens. However, unless you have very big documents, only pre-translate will really be affected.