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.
Find does not locate Cursor on first Occurrence It appears that even after changes in version 7.1, the following error is observable: If the [Enter] key is pressed after the find string is entered in the search bar, then the [Enter] key is ignored if the editor is not fast enough to scroll to the first occurrence of the string before the [Enter] key is pressed. Therefore there is no reliable way to locate on the first occurrence of the find string which is the primary purpose of the command. There are many possible reason why the editor is not fast enough e.g. scanning in progress, refactoring in progress etc.. But that is not my point, the point is that this is a racing condition that should not exist in the first place. The error is never repeatable because on the second try, there is some cacheing going on and the response is instant.
This will need a lot of work in implementation, I plan to change some implementation background in next release. IMHO It should be P3
I don't agree with the priority. The only workaround is not to use the find function which is not acceptable. Please let me explain. The only way I can use the IDE is to do some work e.g. refactoring. In response the only thing the IDE must do is scanning. So if the IDE is scanning which in my case it always does then I cannot use the find function. I must use the find function and in order to use it I must use the {Enter] key. Very simple, best case scenario.
I cannot reproduce it as well. There should be no connection between text search and scanning. The problem is probably triggered by something else. Did the file changed recently before this problem occurred? Is there some other application touching the files? Are the files stored locally on disk or remotely? Can you attach some screen shot, where is visible, how search misses some occurrences? I understand your pain but according to priority guideline I agree with P3 as mkristofic suggested. Only few users can reproduce this problem. Anyway we'll try to track this problem and fix it asap. to MackSix: are you able to reproduce it? Can you provide the requested information as well? Thanks
Actually I was just interested on any updates to this. I see that I voted for it too. I am not sure why I voted for it. It was late at night... maybe it was out of benevolence toward bht. :)
I am running out of time making a testcase for this. However while trying, I found another issue 203985 with the find bar.