┌   ┐
54
└   ┘

summaryrefslogtreecommitdiff
path: root/src/protocolcombo.cpp
diff options
context:
space:
mode:
authorDavid Faure <[email protected]>2007-03-26 21:01:35 +0000
committerDavid Faure <[email protected]>2007-03-26 21:01:35 +0000
commitc6bc5511a8ba05d8f44217b404d615d4d56bb53f (patch)
tree5b0472ad8a44500ec11d781e04574a9defa39659 /src/protocolcombo.cpp
parent581a2b1c642ae259a2e0990a5ea7bef3286cd412 (diff)
cleanups
svn path=/trunk/KDE/kdebase/apps/; revision=646900
Diffstat (limited to 'src/protocolcombo.cpp')
-rw-r--r--src/protocolcombo.cpp3
1 files changed, 3 insertions, 0 deletions
diff --git a/src/protocolcombo.cpp b/src/protocolcombo.cpp
index 3fbf3de55..729102973 100644
--- a/src/protocolcombo.cpp
+++ b/src/protocolcombo.cpp
@@ -42,6 +42,9 @@ ProtocolCombo::ProtocolCombo(const QString& protocol, UrlNavigator* parent)
//TODO: wow this is ugly. or .. is it? ;) we need a way to determine
// if a protocol is appropriate for use in a file manager. hum!
//if (KProtocolInfo::capabilities(*it).findIndex("filemanager") == -1)
+
+ // DF: why not just supportsListing?
+
if (KProtocolInfo::protocolClass(*it) == ":" ||
!KProtocolManager::supportsWriting(*it))
{