ok, I understand. but I am not sure the current setting works in any given workflow that makes intensive use of searches.
in my case, I was proofreading the ja mini and each time I found a glitch, I'd instanciate a search window with the string and would not search right there but only when I am done checking one full document to not loose track of where I am at.
in the case where people do one search at a time the current setting works all right, but then, what i propose would not conflict with such worflow and would ease the workflow for people who do searches in batches.
what do you you think ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
changing the defauts of the search windows is done either
1) by closing a modified window before instanciating a new one
or
2) by instanciating a new one according to the parameters of the lastly opened search window
It seems to me 2) is more what is expected, since defaults are rarely what the user has choosen "by default".
JC
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The settings are saved after each search.
Settings are still saved also when closing the window.
That means that, when opening a new search window, the last saved settings (either from a search or from closing a window) will be used.
That doesn't affect already opened windows.
Didier
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=545103
Originator: NO
Let me see if I get this correctly:
1) Let's assume the current remembered setting is exact search
2) You open a search window, you select keyword search
3) You open another search window (you don't close the first), exact search is selected again
Right?
Then, if you would 4) close the first window, and open another, you would notice that that keyword search would be selected.
Thing is, those settings are only saved when you close a window, not the moment when you change those settings.
Try:
1) Open a search window, select keyword search
2) Close the window
3) Open another, see if keyword search is selected (should be)
If it is, settings are remembered correctly, and this bug is invalid :)
Logged In: YES
user_id=915082
Originator: YES
ok, I understand. but I am not sure the current setting works in any given workflow that makes intensive use of searches.
in my case, I was proofreading the ja mini and each time I found a glitch, I'd instanciate a search window with the string and would not search right there but only when I am done checking one full document to not loose track of where I am at.
in the case where people do one search at a time the current setting works all right, but then, what i propose would not conflict with such worflow and would ease the workflow for people who do searches in batches.
what do you you think ?
Logged In: YES
user_id=1343245
Originator: NO
It's definitely not a bug (i.e., settings are saved when the window is closed).
I'm moving to RFE for possible discussion (with a corresponding title change).
Didier
Logged In: NO
To summarize the discussion:
changing the defauts of the search windows is done either
1) by closing a modified window before instanciating a new one
or
2) by instanciating a new one according to the parameters of the lastly opened search window
It seems to me 2) is more what is expected, since defaults are rarely what the user has choosen "by default".
JC
Implemented in SVN (/trunk).
The settings are saved after each search.
Settings are still saved also when closing the window.
That means that, when opening a new search window, the last saved settings (either from a search or from closing a window) will be used.
That doesn't affect already opened windows.
Didier
Closing...
This feature was implemented in the released version 2.1.5 update 1 of OmegaT.