From e80e396f5daf110497fc6a705a42b66dc1263d83 Mon Sep 17 00:00:00 2001 From: jules Date: Tue, 28 Jan 2014 11:56:42 +0000 Subject: [PATCH] Improved documentation. --- modules/juce_core/files/juce_DirectoryIterator.h | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/modules/juce_core/files/juce_DirectoryIterator.h b/modules/juce_core/files/juce_DirectoryIterator.h index 2f624b3853..3ca2265f1a 100644 --- a/modules/juce_core/files/juce_DirectoryIterator.h +++ b/modules/juce_core/files/juce_DirectoryIterator.h @@ -37,11 +37,11 @@ A DirectoryIterator will search through a directory and its subdirectories using a wildcard filepattern match. - If you may be finding a large number of files, this is better than - using File::findChildFiles() because it doesn't block while it finds them - all, and this is more memory-efficient. + If you may be scanning a large number of files, it's usually smarter to use this + class than File::findChildFiles() because it allows you to stop at any time, rather + than having to wait for the entire scan to finish before getting the results. - It can also guess how far it's got using a wildly inaccurate algorithm. + It also provides an estimate of its progress, using a (highly inaccurate!) algorithm. */ class JUCE_API DirectoryIterator {