0003880: TreeView can sometimes hold bad selection references

ID	Project	Category	View Status	Date Submitted	Last Update

0003880	DarkRadiant	GUI	public	17.10.2014 04:48	07.07.2015 09:26

Reporter	greebo	Assigned To	greebo
Priority	normal	Severity	crash	Reproducibility	sometimes
Status	closed	Resolution	fixed
Product Version	2.0.0
Target Version	2.0.1	Fixed in Version	2.0.1

Summary	0003880: TreeView can sometimes hold bad selection references
Description	An assertion this is possible when a replacement treemodel is associated to the view. The wxDataView::AssociateModel implementation does not fire a cleared event when a new non-NULL model is associated to it - this may leave stale selection pointers in the wxDataViewMainWindow backend. Asssociating a NULL model is safe. Calling associate twice with the same model does not lead to a crash, but a new redundant notifier is attached to the model (number of notifier count increases with each AssociateModel call). Calling AssociateModel with a new replacement model on a treeview that already had a model associated may lead to a crash when calling GetSelection() afterwards and the user had something selected beforehand ("invalid item in selection - bad internal state").
Tags	No tags attached.

Date Modified	Username	Field	Change
17.10.2014 04:48	greebo	New Issue
17.10.2014 04:48	greebo	Status	new => assigned
17.10.2014 04:48	greebo	Assigned To	=> greebo
17.10.2014 05:48	greebo	Note Added: 0007073
17.10.2014 05:48	greebo	Status	assigned => resolved
17.10.2014 05:48	greebo	Fixed in Version	=> 2.0.1
17.10.2014 05:48	greebo	Resolution	open => fixed
07.07.2015 09:26	greebo	Status	resolved => closed

greebo 17.10.2014 05:48 administrator ~0007073	Additional code added which should prevent further crashes. It might still be possible that internal notifiers are stacking up in the wxDataViewModel.