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.
Summary: | Go to Function or Variable cannot find class members? | ||
---|---|---|---|
Product: | cnd | Reporter: | eskild <eskild> |
Component: | Navigation | Assignee: | issues@cnd <issues> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
eskild
2008-06-11 12:22:26 UTC
I've recategorized the IZ to an enhancement since it is unclear how the workflow needs to be modified to address the particular situation described. It would be helpful to get a sense of how you'd like the product to behave when the symbol type is "unknown". How about this: Replace the current feature with a "Go to Symbol" box. In it, we have the same elements as we currently do (but see (*), below), but we add a set of checkboxes: Search in: [x] Class names [x] Class member variables (<-- perhaps also separate entries for static members?) [x] Class member functions [ ] C-style Variables [ ] C-style Functions [ ] typedef's ...etc... Generally utilize the power of the C/C++ parser [ ] All of the above So now there's no "unknown" symbol types, and the user gets the option of narrowing in on his/her search. Furthermore, we get rid of the "Go to Type" dialog; its functionality is neatly folded into this one. Optionally, one could add some presets: "C++ construct", "Types only", "Functions only" and the like. But that's not essential. (*): When results are displayed in the "Elements Found" list, there must be a column indicating what the actual type of symbol is. |