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: | Always show source node's properties when it is being edited | ||
---|---|---|---|
Product: | java | Reporter: | Ben Hutchison <benhutchison> |
Component: | Unsupported | Assignee: | Chris Ledantec <cledantec> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Windows ME/2000 | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Bug Depends on: | 6559 | ||
Bug Blocks: |
Description
Ben Hutchison
2002-03-05 15:44:28 UTC
Set target milestone to TBD Set target milestone to TBD reassigne to David K., new owner of editor Moving to Java. Is this Java module's issue? Im not sure. The property sheet must be getting some signal from the editor to tell it to synch with the method, class decl, etc. I want to be able to suppress this signal so I can see the top level node properties always. David is right (D. - thanks for catching the RFE). Java Editor "active" node is the one most specific for the place in the Editor - e.g. method node or field node. While I can not really change that (other actions depend on precise context to be present), the merge could be possible done. However I am not sure whether it applies in the new project system which uses execution profiles rather than execution on specific objects in the Explorer tree. depends on keeping editor/explorer focus in synch. It does not depend on the Explorer / editor sync at all. Please read the original request and observe the current global property sheet behaviour while editing/navigating through a java source. With the new buildsystem, there are no longer any interesting properties on the file that would make sense to display when the source is being edited. Reorganization of java component |