Community
Participate
Working Groups
The Text search dialog fills in the extensions field with the extension of the active editor. With the NLS work, I'm often looking at a .properties file, but want to search .java files. I always have to override the default in this case. It would be better if it simply remembered the last setting, rather than trying to match extensions. NOTES: DM (8/2/01 2:49:00 PM) The extension is also used to bring the right search page to front. If I work on a Java file and press search I would expect the Java search page to be in brought to front. I assumed this use case to be more often used than the one described above.
moved to 'active'
PRODUCT VERSION: 0.9
so the proposal is to leave as is?
Yes. Proposal is to leave as is because all search stuff is input centric. We also try to set the fields (Search Expression, Search For, Limit To) from the current selection. In my opinion the 80% case is that if you select something and then press search, that you give it a context and that you expect the corresponding search page being in front and filled accordingly. Using previous values in the text search page would not fix the described problem since the wrong page is in front in the first place. Suggest to close.
Feels like to do better we'd need to know that entries in .properties files are often referenced by .java files. Feel free to close if you don't think using previous settings is better.
Visited it again. Leave as is. Opening the text search for .properties makes sense. What about a checkbox on the search page or a preference: [x] Switch to page based on selection
I'd prefer not to introduce another option. I can live with the current behaviour. Can close PR.
That's ok for me.
