Change Details

OS: all plattforms. QmitkDataStorageTreeModel can cause invalid pointer exceptions due to insufficient validity check for QModelIndex. This situation can occure e.g. when following conditions are met: # multiple selection models are used # the application closes => the content of the data storage is removed node by node # the tree model is already updated # the selection model/view requests information about a node that is allready removed from the storage (and the internal model tree). I guess we rarely see this problem because the QmitkDataStorageTreeModel is normaly used only once in the workbench. With the new selection concept this changes. You can see how to fix the problem in the QmitkDataStorageSimpleTreeModel. Due to the fact, that the QmitkDataStorageTreeModel has several other serious design issues, I think it is not worth to fix it there (as long it is just used by the DataManager). We should sooner or later deprecate QmitkDataStorageTreeModel and move to better models. This is why I propose the set it into state "wont fix" and understand this task as issue documentation.

OS: all plattforms. QmitkDataStorageTreeModel causes invalid pointer exceptions when using it with invalid QModelIndex instances due to insufficient validity checking. This situation can occure e.g. when following conditions are met: # multiple selection models are used # the application closes => the content of the data storage is removed node by node # the tree model is already updated # the selection model/view requests information about a node that is allready removed from the storage (and the internal model tree). I guess we rarely see this problem because the QmitkDataStorageTreeModel is normaly used only once in the workbench. With the new selection concept this changes. You can see how to fix the problem in the QmitkDataStorageSimpleTreeModel. Due to the fact, that the QmitkDataStorageTreeModel has several other serious design issues, I think it is not worth to fix it there (as long it is just used by the DataManager). We should sooner or later deprecate QmitkDataStorageTreeModel and move to better models. This is why I propose the set it into state "wont fix" and understand this task as issue documentation.

OS: all plattforms. QmitkDataStorageTreeModel can causeuses invalid pointer exceptionstions when using it with invalid QModelIndex instances due to insufficient validity check for QModelIndexing. This situation can occure e.g. when following conditions are met: # multiple selection models are used # the application closes => the content of the data storage is removed node by node # the tree model is already updated # the selection model/view requests information about a node that is allready removed from the storage (and the internal model tree). I guess we rarely see this problem because the QmitkDataStorageTreeModel is normaly used only once in the workbench. With the new selection concept this changes. You can see how to fix the problem in the QmitkDataStorageSimpleTreeModel. Due to the fact, that the QmitkDataStorageTreeModel has several other serious design issues, I think it is not worth to fix it there (as long it is just used by the DataManager). We should sooner or later deprecate QmitkDataStorageTreeModel and move to better models. This is why I propose the set it into state "wont fix" and understand this task as issue documentation.