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.
I was several times confused by the the 111C/101 badges in the explorer, I thought these were errors because they are red. Can we change their color to something else than red? Here's a record from another user who got confused by them: ------------------%<-------------------- On a related note, forcing a syntax error in the source editor causes the red box with a white x to appear in the margin. Hovering there produces a tooltip explaining the error. Slightly before the red box with white x appears, the little red error icon that looks something like 111C/101 appears beside the file in the Projects tab. I.e., the Projects tab seems to know about the error slightly sooner than does the editor pane. However, while deleting the change in the source that resulted in the error removes the red box with the white x, indicating that the source is good again, the 111C/101 annotation remains in the Projects tab. It seems that some communication of source goodness has been lost between the source editor and the Projects tab. Saving the edited file removes the asterisk from that file's tab in the editor pane but still doesn't remove the 111C/101 annotation. It takes a rebuild of the project, or at least a recompile of that file, to remove the 111C/101 icon. By the way, I also cannot find documentation of the 111C/101 icon, though it's pretty obvious what it means. However, since there were some questions and answers in the mailing list archives explaining the meaning, perhaps that meaning is not quite as obvious as I just claimed. So that's another reason that some kind of tooltip for the different possible icons in the Projects tab could be useful, especially for new users. Maybe a "total newbie" mode is needed. ------------------%<--------------------
Jano?
I agree, we'll change the symbol or we would get rid of this function completely. I suspect it's not very useful the indication isn't propagated up to the project node.
Solved, to my knowledge.