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 114104 - Propagate broken #include badge to folders that contain broken files
Summary: Propagate broken #include badge to folders that contain broken files
Status: NEW
Alias: None
Product: cnd
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: Sun All
: P3 blocker (vote)
Assignee: Alexander Simon
Depends on:
Reported: 2007-08-29 11:38 UTC by Vladimir Kvashin
Modified: 2009-11-12 05:58 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Kvashin 2007-08-29 11:38:36 UTC
Now, as soon as broken #include directive is encountered, an error badge appears on the project node.
It would be fine if error badges appeared on the nodes that correspond to particular files and folders that contain that

This would be consistent with NetBeans, which acts the same way with Version Control badges, for example.
Comment 1 Vladimir Kvashin 2007-08-29 11:40:51 UTC
Implementation comment:
this affects both highlight module and project system.
(that's why I left "other" in subcomponent field).

Comment 2 Alexander Simon 2007-08-31 07:55:29 UTC
Stepan Doubrava opinion:
I believe the tooltip is the key thing to have with the broken include ... the badge is so small that it can only show
something is wrong, but more detail explanation can only be provided by the tooltip. Moreover if we have too many
different badges users will be confused which means what.

I think the ideal functionality would be following:
If there is unresolvable item ("test.h") it should be marked with the badge showing something is wrong, when hovering
over the item it should show a tooltip explaining the problem ("test.h can't be found").
Same badge should be added to the item's folder ("Header files") and again tooltip should explain the problem
("unresolved file test.h") if there is more missing files it could tell first 3 and then "...".
Same badge should also propagate to the project icon with toolip explaining the problem ("Unresolved headers").
I believe propagating the problem through the structure is good, because when all the nodes are collapsed user would
have to open all the nodes to find the unresolved item.

I thing all the badges should be same. (I appreciate your badge, because it is very distinctive, but I thing it is
better to be consistent)