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 259042 - OutlinewView model automatically resets itself on remove notify
Summary: OutlinewView model automatically resets itself on remove notify
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Outline&TreeTable (show other bugs)
Version: 8.1
Hardware: PC Linux
: P3 normal with 3 votes (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-28 08:41 UTC by scanti
Modified: 2016-04-28 08:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Test case (4.34 MB, application/x-bzip)
2016-04-28 08:41 UTC, scanti 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description scanti 2016-04-28 08:41:10 UTC 
Created attachment 159456 [details]
Test case

We are using your OutlineView Model in our RCP application and when we moved to NB RCP 8.1 we found out that maximizing the TopComponent in whom the OutlineView was put, made the OutlineView resets its model. This also happens when you drag the  TopComponent to another mode. 

We took a look at the code and we noticed that you call setModel(null) in the removeNotify method of org.netbeans.modules.viewmodel2.OutlineTable. 

We understand that you do this to avoid memory leaks, but this is giving us some problems. IMHO it should the one that sets the model to reset it and not be hidden in the API (see org.netbeans.modules.debugger.ui.views,View where only addNotify is overridden) .

We made a workaround in our application and we are looking forward to see a better fix in the future.

The problem was introduced with https://netbeans.org/bugzilla/show_bug.cgi?id=250636