aboutsummaryrefslogtreecommitdiffstats
path: root/src/plugins/find/ifindfilter.cpp
diff options
context:
space:
mode:
authorNikolai Kosjar <nikolai.kosjar@digia.com>2013-10-07 13:34:40 +0200
committerNikolai Kosjar <nikolai.kosjar@digia.com>2013-10-10 15:56:12 +0200
commitb8dbac0b9c4c45ee0d17d16eeae9086a14e9656a (patch)
tree784eb7872148f25bbe34a650b7c152e990ede927 /src/plugins/find/ifindfilter.cpp
parenta48315ee1f5372cacc749a2cf985f55d1e312dbd (diff)
Rename "[Mm]ethod(s)" to "[Ff]unction(s)"
Only methods as programming functions are affected. Besides renaming some actions like "Switch Between Function Declaration/Definition" this mostly touches (api) code comments. This is a follow-up patch to commit 872bfb7. Change-Id: Icb65e8d73b59a022f8885b14df497169543a3b92 Reviewed-by: hjk <hjk121@nokiamail.com>
Diffstat (limited to 'src/plugins/find/ifindfilter.cpp')
-rw-r--r--src/plugins/find/ifindfilter.cpp16
1 files changed, 8 insertions, 8 deletions
diff --git a/src/plugins/find/ifindfilter.cpp b/src/plugins/find/ifindfilter.cpp
index 06754f9ca0..7755d7088d 100644
--- a/src/plugins/find/ifindfilter.cpp
+++ b/src/plugins/find/ifindfilter.cpp
@@ -74,20 +74,20 @@
The common pattern is roughly this:
- Implement the actual search within a QtConcurrent based method, that is
- a method that takes a \c{QFutureInterface<MySearchResult> &future}
+ Implement the actual search within a QtConcurrent based function, that is
+ a function that takes a \c{QFutureInterface<MySearchResult> &future}
as the first parameter and the other information needed for the search
as additional parameters. It should set useful progress information
on the QFutureInterface, regularly check for \c{future.isPaused()}
and \c{future.isCanceled()}, and report the search results
(possibly in chunks) via \c{future.reportResult}.
- In the find filter's find/replaceAll method, get the shared
+ In the find filter's find/replaceAll function, get the shared
\gui{Search Results} window, initiate a new search and connect the
signals for handling selection of results and the replace action
(see the Find::SearchResultWindow class for details).
Start your search implementation via the corresponding QtConcurrent
- methods. Add the returned QFuture object to the Core::ProgressManager.
+ functions. Add the returned QFuture object to the Core::ProgressManager.
Use a QFutureWatcher on the returned QFuture object to receive a signal
when your search implementation reports search results, and add these
to the shared \gui{Search Results} window.
@@ -138,13 +138,13 @@
\fn bool IFindFilter::isReplaceSupported() const
Returns whether the find filter supports search and replace.
- The default value is false, override this method to return \c true, if
+ The default value is false, override this function to return \c true, if
your find filter supports global search and replace.
*/
/*!
\fn void IFindFilter::findAll(const QString &txt, Find::FindFlags findFlags)
- This method is called when the user selected this find scope and
+ This function is called when the user selected this find scope and
initiated a search.
You should start a thread which actually performs the search for \a txt
@@ -161,9 +161,9 @@
/*!
\fn void IFindFilter::replaceAll(const QString &txt, Find::FindFlags findFlags)
- Override this method if you want to support search and replace.
+ Override this function if you want to support search and replace.
- This method is called when the user selected this find scope and
+ This function is called when the user selected this find scope and
initiated a search and replace.
The default implementation does nothing.