[ BUILD # : beta 2 ]
[ JDK VERSION : 1.5.* ]
The radio buttons that used to appear in search results are no longer
present. This is a regression and should be repaired.
If you search across a large number of files for all occurrences of a
string, the results are very difficult to read if the file names are
Confirmed. Postponed for an update release (e.g. an updated module published on the update centre) or to the next release.
This is a *really* inconvenient regression. I use Find quite a bit in larger projects, particularly as a way to locate
classes that have I know belong to a particular named 'family', and without a sort capability it severely hampers being
able to zero in on which result is the one I want to open.
I have created an initial implementation of sorting by name. I committed it to CVS branch "results_sorting". I only
tested it very briefly and made only a very simple UI which is far from perfect (just two radio-buttons at the bottom of
search results). Feel free to polish it.
Created attachment 52985 [details]
binary patch for NB 6.0
I have attached a binary patch for NB 6.0, providing the mentioned initial implementation of sorting search results.
To apply it, put the attached file ("binary-patch-bug119818-NB6.0.jar") to subdirectory
of your NetBeans installation directory. (Not tested, feedback welcome.)
Thanks very much for working on this!
The contents of the search results window disappear when scrolled, and this exception is reported:
java.lang.IndexOutOfBoundsException: Index: 25, Size: 10
How many matching files were reported in the root node of the search results window in that case? was it closer to 10 or
to 25 (see the numbers reported in the exception)?
I tried to repeat the same test. There are no errors and the results scroll normally until I click the "Sorted by Name"
button, then the red exception indicator in the lower right lights up even before I try to scroll. The search reported
46 matches in 26 files. The exception had the same text: java.lang.IndexOutOfBoundsException: Index: 25, Size: 10.
I see. This happens if there are multiple files of the same name (in different directories).
I fixed the bug with the IndexOutOfBoundsException.
Created attachment 53012 [details]
updated binary patch for NB 6.0
I have updated an updated binary patch - it should solve the issue with the IndexOutOfBoundsException.
Works great now, thanks again!
Will this go into 6.1? 6.0.1?
I do not know the rules for integrating bugfixes into patch releases of NB 6.0. So I do not know at the moment.
I added the "REGRESSION" keyword (as this actually is a regression) which might increase the chance.
This is a regression but it requires a UI change. The button was removed when search&replace was implemented - and the
Replace button added. If the Replace button is displayed, it is at the same position as the sorting radio buttons were -
so this must be resolved first. I will not make such a UI change in NB 6.1 - I have more important fixes to do.
this is very annoying with a large hitlist ...
Since this functionality was removed by Marian Petras while rewriting the results tree for replace functionality it
looks for me as a new feature implementation. And this is out of scope for the 7.0 now. Of course if I have time I would
fix it for 7.0.
Andrey Yamkovoy agreed that he would review and integrate a patch for this issue contributed by the NetFIX  team.
I started it and will attach the patch soon. More tests needed.
Created attachment 85100 [details]
I attached an proposed patch. Comments and review are welcome.
1. What you think, "Unsort" could be good for? Likely you could save footprint + GUI space on having only 1 toggle button.
Instead of "Unsort", IMO there were more interesting options: Sort by [simple name | full package name | source root |
2. Am I right, that you want to perform partly sort, before search is entirely completed?
- be aware, if setSorted() is thread-safe against concurrently searching thread. (I guess it should be interrupted while
copying from matchingObjects).
- sortedMatchingObjects.containsAll(matchingObjects) could become expensive operation on ArrayList.
-- maybe comparing size of both list's would suffice, as size of matchingObjects likely never decreases.
-- containsAll() would be faster on SortedSet for sortedMatchingObjects.
- you could save clear() and sort() if using SortedSet for sortedMatchingObjects, and can do partly addAll(), if saving
last used size of matchingObjects for start index of addAll().
- I you waive from "Unsort", you could save copying to sortedMatchingObjects and directly sort matchingObjects, even
partly, if search thread is interrupted while sorting.
> - I you waive from "Unsort", you could save copying to sortedMatchingObjects and directly sort matchingObjects, even
> partly, if search thread is interrupted while sorting.
In this case Collections.sort() may be faster than collecting results in SortedSet. Should be tested.
If partly sort is performed often, I guess collecting results in SortedSet should be faster than repeated full
Collections.sort(), as method setSorted() only should run UPDATE_SORTED_CHILDREN_TASK.
From the user point of view:
- The "Unsort" function does not make sense. Agree with ulfzibis. In my opinion the list always should be sorted by name
but grouping (simple name, phisical view, logical view etc) should be based on the user choice.
- The grouping contols should be placed on the toolbar in the left side of output window to have more space for search
results. Existing buttons in the bottom should be moved to it too (see issue 169129).
As for the code the comments from ulfzibis looks reasonable and should be investigated and probably "integrated" into
Michel, can you please improve the patch in accordance with recent comments from Ulf? Thanks a lot!
Okey, I will make some changes and post the new patch as soon as possible. BTW, I just used the same UI in previous
version as users could know. The unsort button just show the results as original, just after search is finished.
In my original tests, the sort is possible just when search is finished. The button should be disabled during search.
Thanks for the comments.
This issue has very clear explanation: "the results are very difficult to read if the file names are not sorted".
I don't see any benefits if the search results will have an unsorted representation.
I guess, if the list of files will always be sorted according to their names then this issue will be completely resolved.
Note, such solution doesn't require any UI changes, and the display space will be used for results, but not for controls that will be used rarely (or even never!).
Well, I agree with Victor, we don't need any UI change if the behaviour was to order by file names. If you agree about it, I can provide an patch soon.
Created attachment 93540 [details]
Well, I changed my patch to doesn't change anything in UI, just reorder the view when any new object is found. I need to make more performance tests but looks good for now. I would like to ask you to review it, any comment and improvement are welcome.
Andrey, can you please review the patch and integrate it if you don't find any problems? Thanks!
Hi Jirka, Michel,
Victor is going to care about this issue. However I could not promise that this will happen prior to M1 :)
No problem Alexei. Just don't forget to integrate the patch to trunk before 6.9 is branched, please. Thanks!
The proposed patch (id=93540) has been applied.
Thanks a lot Victor. And of course thanks Michel for the patch!
Integrated into 'main-golden', will be available in build *201002040200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Victor G. Vasilyev <firstname.lastname@example.org>
Log: #119818 - [60cat] search results sort buttons gone. The patch with id=93540 has been applied.
The patch destroys logic of both actions "Go to previous matching string" and "Go to next matching string" due to different orders in the lists of elements in view and model.
Temporarily the fix is reverted.
Is there someone looking this or could I take care of it? BTW, thanks for the rolback in time.
Integrated into 'main-golden', will be available in build *201003190200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Victor G. Vasilyev <email@example.com>
Log: Regression after fix #119818. Temporarily the fix is reverted.
Fixed again in the main trunk
(In reply to comment #38)
> Is there someone looking this or could I take care of it?
If you have interest in the resolving of this issue then, could you please, test the search feature after my changes to be sure that all is OK.
(In reply to comment #41)
> (In reply to comment #38)
> > Is there someone looking this or could I take care of it?
> If you have interest in the resolving of this issue then, could you please,
> test the search feature after my changes to be sure that all is OK.
thanks for your fix. I tested all features I could but looks like click 'Show All Details' action nothing is shown at output tab.
Should we reopen it or file another issue, since I can't found any problem at search ordering, it is awesome now.
v. Build 100322-8d160876e56c
(In reply to comment #42)
Thanks for the testing.
Please, file a separate bug report against utilities/Search if the 'Show
All Details' action issue exists.
I can reproduce the 'Show All Details' action issue.
The bug 182540 has been filed.
I agree. Thanks for your really quick fix. Marking this as verified and will be a pleasure to verify the another one too. Thanks again.