This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Find in projects: unintuitive behavior for "Last: Open Projects" | ||
---|---|---|---|
Product: | utilities | Reporter: | terje7601 |
Component: | Search | Assignee: | Jaroslav Havlin <jhavlin> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 8.1 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Draft of the fix |
Description
terje7601
2015-06-16 08:43:25 UTC
> However, this doesn't use a "refreshed" list of projects. This is the currently intended behavior. But I understand it is confusing. > This is unintuitive & it took me quite a while to figure out why NetBeans > didn't find what I was looking for. This should be improved. The idea behind the current behavior is to use the same static list of directories when search is refreshed and scope "Last" is selected. So, if the last scope was "Selection", the scope will be the same when refreshing, even if the actual selection has changed (which is correct, I think). For "Last: Open Projects", it works the same. To use current open projects, users need to change scope to "Open Projects". Similar case is "Current Project" (which is also correct I thing, we don't want to update the last search scope if file from another project is selected in the IDE). I'm not sure what is correct for "Last: Open Projects". I've made a small internal poll and it was quite balanced. I'll need to ask more people. Maybe we could add number of open project to name of the scope (so it would be "Last: Open Projects (5)"). But it is not very helpful if number of open projects is high. Note: The (refresh) button title is "Modify Criteria", which is more exact than "Refresh". Search criteria can be changed, but search scope is preserved. Maybe the icon is confusing. Thank you for reporting. Created attachment 155214 [details]
Draft of the fix
Possible fix - if we decide to change the behavior. Needs to be tested. Also impact on API clients (that may rely on immutability of SearchInfo instances) should be evaluated.
Another option would be to add some "update" method to search info, which would return new updated instance if needed.
Note: Workaround is using Ctrl+Shift+F for opening the Find dialog. Search scope as well as other parameters are persisted. |