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.

Bug 29727 - Manage category nodes better
Summary: Manage category nodes better
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Hints & Annotations (show other bugs)
Version: 3.x
Hardware: Sun SunOS
: P3 blocker (vote)
Assignee: Torbjorn Norbye
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-26 00:10 UTC by Torbjorn Norbye
Modified: 2003-02-17 21:56 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Torbjorn Norbye 2002-12-26 00:10:36 UTC
There are two problems with the category nodes today:

* First, category nodes are not removed when the
number of suggestions goes down to zero.  A recent
API change makes it a lot easier to make that
happen now, since we now know the difference
between a remove followed by an add, and a remove
followed by nothing.

* Second, when you switch to a different file,
there's a brief pause (2 seconds) when the
providers don't do anything; then they kick into
gear. This is so that quick file traversal will
not cause suggestion updates.  However, when you
switch away from a file, the suggestions are
removed immediately. Thus, there's an interval
when you see "(0)" (zero-count) after each file,
even though the true state is "(updating)". 
Implementing something like that - either remove
the count entirely (and show it when the scan is
performed) or do something more explicit. The key
is for the user to know the difference between
"this file has no suggestions" and "this file
hasn't been scanned yet, wait another second".
Comment 1 Torbjorn Norbye 2002-12-31 18:32:05 UTC
I've sort of fixed the second problem: I now remove the (0) part when
you hide a file.  The only thing that isn't fixed is that for files
where the scan results in 0 hits, you don't get (0) next to the
category node. That's because these providers never call register with
a null add list, which would have caused (0) to appear. However, I'm
no sure I should fix that since part 1 of this issue asks for those
category nodes to be removed in the first place.
Comment 2 Torbjorn Norbye 2003-01-20 16:54:09 UTC
This has now been fixed. However, I would also like to preserve the
type order in a better way, so I'm leaving this issue open to track that.
Comment 3 Torbjorn Norbye 2003-02-17 21:56:53 UTC
The type-ordering was fixed a while ago, with this commit message:
* Fix suggestion type ordering. The suggestions should stay in a fixed
  order now - which I've set up roughly according to "importance":
      Compilation Errors
      Tasks Due
      Rule Violations
      HTML Problems
      Source Tasks
      Javadoc Problems
      Copyright Problems