From af820f077b0d311ad99d3736015d62a081dea92d Mon Sep 17 00:00:00 2001
From: Peter Penz <peter.penz19@gmail.com>
Date: Sat, 9 Oct 2010 10:14:12 +0000
Subject: [PATCH] It is a valid usecase that the model can be 0 when
 destructing a view.

svn path=/trunk/KDE/kdebase/apps/; revision=1184156
---
 src/views/dolphinviewcontroller.cpp | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/src/views/dolphinviewcontroller.cpp b/src/views/dolphinviewcontroller.cpp
index 6ef32f07fc..f82b6755a5 100644
--- a/src/views/dolphinviewcontroller.cpp
+++ b/src/views/dolphinviewcontroller.cpp
@@ -197,9 +197,13 @@ KFileItem DolphinViewController::itemForIndex(const QModelIndex& index) const
     Q_ASSERT(m_itemView != 0);
 
     QAbstractProxyModel* proxyModel = static_cast<QAbstractProxyModel*>(m_itemView->model());
-    KDirModel* dirModel = static_cast<KDirModel*>(proxyModel->sourceModel());
-    const QModelIndex dirIndex = proxyModel->mapToSource(index);
-    return dirModel->itemForIndex(dirIndex);
+    if (proxyModel != 0) {
+        KDirModel* dirModel = static_cast<KDirModel*>(proxyModel->sourceModel());
+        const QModelIndex dirIndex = proxyModel->mapToSource(index);
+        return dirModel->itemForIndex(dirIndex);
+    }
+
+    return KFileItem();
 }
 
 void DolphinViewController::triggerItem(const QModelIndex& index)