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: | Navigator Window ignores filterable/sortable configuration of StructureScanner | ||
|---|---|---|---|
| Product: | editor | Reporter: | matthias42 |
| Component: | CSL (API & infrastructure) | Assignee: | Milutin Kristofic <mkristofic> |
| Status: | VERIFIED FIXED | ||
| Severity: | normal | Keywords: | PATCH_AVAILABLE |
| Priority: | P3 | ||
| Version: | 7.4 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Bug Depends on: | 239907 | ||
| Bug Blocks: | |||
| Attachments: |
Screenshot of the Problem
proposed patch v1 |
||
Created attachment 143553 [details]
proposed patch v1
Good insight, thank you. I pushed your patch to repository http://hg.netbeans.org/jet-main/rev/c313fda86661 Integrated into 'main-silver', will be available in build *201402010001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/48dc63649ec0 User: Milutin Kristofic <mkristofic@netbeans.org> Log: #239906 - Navigator Window ignores filterable/sortable configuration of StructureScanner |
Created attachment 143552 [details] Screenshot of the Problem I implemented language support for the property list ascii format and while doing so, I also implemented a structure scanner. While the navigator window works, I also noticed, that my configuration (enabled sorting, disabled filtering) was ignored): public class PListStructureScanner implements StructureScanner { [...] @Override public Configuration getConfiguration() { return new Configuration(true, false); } [...] } I had a look at the CSL Sourcecode and the problem lies in the fact, whether the filter menu and actions are created is dermined in the constructor, which is invoked with null as language and this leads to the default creation with the filter panel and actions. I moved that functionality out of the constructor (for compatibility reasons it is still called there) and added it to the case when the navigator is refreshed for a exchanged fileObject.