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.
Here is the problem description: I have a project which is time expensive to parse (let's say about 20 minutes). I am opening some file and opening quick navigator ==> if file is not parsed yet the list will be empty and it is kind of annoying. Even if I will edit file I will have empty list until saving. Meanwhile if I will invoke code completion or hyperlink in this file it will be parsed (popped in the queue) and quick navigator list will be filled in very quickly. From the user point of view opening file in editor is the signal to parser to parse this file faster and show quick navigator filled in (in NetBeans when you open Java source file Navigator will show classes/methods even if you will not touch source file)
I'd agree that opening in the editor is the right signal to raise priority of the file for parser. I'd also suggest to consider the event of switching editor tab to a file to be the highest priority signal for parser.
No such component any more.
The quick navigator component does not exist any more; but the problem does. The same behavior is observed with the standard Navigator. (So I changed the title and reopened instead of creating a new issue, since the issue is *exactly* the same)
Yes, it wold be fine to solve this. However, since the time the issue was filed parsing speed improved immensely; right now I opened MySQL on my laptop and it was parsed within 43 seconds. So now we consider other processes (such as finding references) as slow ones, and make efforts to seed them up; while the time of initial parsing nearly doesn't matter - it's just fast enough. That's why I don't believe this deserves P3.
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. We apologize for any inconvenience. Thank you. The NetBeans Team