1 /////////////////////////////////////////////////////////////////////////////
2 // Name: wx/fswatcher.h
3 // Purpose: wxFileSystemWatcher
4 // Author: Bartosz Bekier
7 // Copyright: (c) 2009 Bartosz Bekier <bartosz.bekier@gmail.com>
8 // Licence: wxWindows licence
9 /////////////////////////////////////////////////////////////////////////////
12 @class wxFileSystemWatcher
14 The wxFileSystemWatcher class allows to receive notifications of file
17 @note Implementation limitations: this class is currently implemented for
18 MSW, OS X and GTK ports but doesn't detect all changes correctly
19 everywhere: under MSW accessing the file is not detected (only
20 modifying it is) and under OS X neither accessing nor modifying is
21 detected (only creating and deleting files is). Moreover, OS X
22 version doesn't currently collapse pairs of create/delete events in a
23 rename event, unlike the other ones.
25 For the full list of change types that are reported see wxFSWFlags.
27 This class notifies the application about the file system changes by
28 sending events of wxFileSystemWatcherEvent class. By default these events
29 are sent to the wxFileSystemWatcher object itself so you can derive from it
30 and use the event table @c EVT_FSWATCHER macro to handle these events in a
31 derived class method. Alternatively, you can use
32 wxFileSystemWatcher::SetOwner() to send the events to another object. Or
33 you could use wxEvtHandler::Connect() with @c wxEVT_FSWATCHER to handle
34 these events in any other object. See the fswatcher sample for an example
35 of the latter approach.
42 class wxFileSystemWatcher
: public wxEvtHandler
48 wxFileSystemWatcher();
51 Destructor. Stops all paths from being watched and frees any system
52 resources used by this file system watcher object.
54 virtual ~wxFileSystemWatcher();
57 Adds @a path to currently watched files.
59 The @a path argument can currently only be a directory and any changes
60 to this directory itself or its immediate children will generate the
61 events. Use AddTree() to monitor the directory recursively.
64 The name of the path to watch.
66 An optional filter to receive only events of particular types.
68 virtual bool Add(const wxFileName
& path
, int events
= wxFSW_EVENT_ALL
);
71 This is the same as Add(), but recursively adds every file/directory in
72 the tree rooted at @a path.
74 Additionally a file mask can be specified to include only files
75 matching that particular mask.
77 This method is implemented efficiently under MSW but shouldn't be used
78 for the directories with a lot of children (such as e.g. the root
79 directory) under the other platforms as it calls Add() there for each
80 subdirectory potentially creating a lot of watches and taking a long
83 virtual bool AddTree(const wxFileName
& path
, int events
= wxFSW_EVENT_ALL
,
84 const wxString
& filter
= wxEmptyString
);
87 Removes @a path from the list of watched paths.
89 virtual bool Remove(const wxFileName
& path
);
92 Same as Remove(), but also removes every file/directory belonging to
93 the tree rooted at @a path.
95 virtual bool RemoveTree(const wxFileName
& path
);
98 Clears the list of currently watched paths.
100 virtual bool RemoveAll();
103 Returns the number of currently watched paths.
105 @see GetWatchedPaths()
107 int GetWatchedPathsCount() const;
110 Retrieves all watched paths and places them in @a paths. Returns
111 the number of watched paths, which is also the number of entries added
114 int GetWatchedPaths(wxArrayString
* paths
) const;
117 Associates the file system watcher with the given @a handler object.
119 All the events generated by this object will be passed to the specified
122 void SetOwner(wxEvtHandler
* handler
);
128 @class wxFileSystemWatcherEvent
130 A class of events sent when a file system event occurs. Types of events
131 reported may vary depending on a platform, however all platforms report
132 at least creation of new file/directory and access, modification, move
133 (rename) or deletion of an existing one.
138 @see wxFileSystemWatcher
139 @see @ref overview_events
143 class wxFileSystemWatcherEvent
: public wxEvent
146 wxFileSystemWatcherEvent(int changeType
, int watchid
= wxID_ANY
);
147 wxFileSystemWatcherEvent(int changeType
, const wxString
& errorMsg
,
148 int watchid
= wxID_ANY
);
149 wxFileSystemWatcherEvent(int changeType
,
150 const wxFileName
& path
, const wxFileName
& newPath
,
151 int watchid
= wxID_ANY
);
154 Returns the path at which the event occurred.
156 const wxFileName
& GetPath() const;
159 Returns the new path of the renamed file/directory if this is a rename
162 Otherwise it returns the same path as GetPath().
164 const wxFileName
& GetNewPath() const;
167 Returns the type of file system change that occurred. See wxFSWFlags for
168 the list of possible file system change types.
170 int GetChangeType() const;
173 Returns @c true if this error is an error event
175 Error event is an event generated when a warning or error condition
178 bool IsError() const;
181 Return a description of the warning or error if this is an error event.
183 wxString
GetErrorDescription() const;
186 Returns a wxString describing an event, useful for logging, debugging
189 wxString
ToString() const;
192 wxEventType wxEVT_FSWATCHER
;
195 These are the possible types of file system change events.
197 Not all of these events are reported on all platforms currently.
203 /// File or directory was created.
204 wxFSW_EVENT_CREATE
= 0x01,
206 /// File or directory was deleted.
207 wxFSW_EVENT_DELETE
= 0x02,
210 File or directory was renamed.
212 Notice that under MSW this event is sometimes -- although not always --
213 followed by a ::wxFSW_EVENT_MODIFY for the new file.
215 Under OS X this event is currently not detected and instead separate
216 ::wxFSW_EVENT_CREATE and ::wxFSW_EVENT_DELETE events are.
218 wxFSW_EVENT_RENAME
= 0x04,
221 File or directory was modified.
223 Depending on the program doing the file modification, multiple such
224 events can be reported for a single logical file update.
226 Under OS X this event is currently not detected.
228 wxFSW_EVENT_MODIFY
= 0x08,
231 File or directory was accessed.
233 This event is currently only detected under Linux.
235 wxFSW_EVENT_ACCESS
= 0x10,
238 A warning condition arose.
240 This is something that probably needs to be shown to the user in an
241 interactive program as it can indicate a relatively serious problem,
242 e.g. some events could have been missed because of an overflow. But
243 more events will still be coming in the future, unlike for the error
246 wxFSW_EVENT_WARNING
= 0x20,
249 An error condition arose.
251 Errors are fatal, i.e. no more events will be reported after an error
252 and the program can stop watching the directories currently being
255 wxFSW_EVENT_ERROR
= 0x40,
257 wxFSW_EVENT_ALL
= wxFSW_EVENT_CREATE
| wxFSW_EVENT_DELETE
|
258 wxFSW_EVENT_RENAME
| wxFSW_EVENT_MODIFY
|
260 wxFSW_EVENT_WARNING
| wxFSW_EVENT_ERROR