Discussion

The URL of the item which changed.

Discussion

An approximate date and time the event occured.

Discussion

Denotes a special event sent when a volume is mounted underneath one of the URLs being watched.

Denotes a special event sent when a volume is mounted underneath one of the URLs being watched. The URL in the event is the URL to the newly-mounted volume. You will receive one of these notifications for every volume mount event inside the kernel (independent of DiskArbitration). Beware that a newly-mounted volume could contain an arbitrarily large directory hierarchy. Avoid pitfalls like triggering a recursive scan of a non-local filesystem, which you can detect by checking for the absence of the MNT_LOCAL flag in the f_flags returned by statfs(). Also be aware of the MNT_DONTBROWSE flag that is set for volumes which should not be displayed by user interface elements.

Discussion

Denotes a special event sent when a volume is unmounted underneath one of the URLs being watched.

Denotes a special event sent when a volume is unmounted underneath one of the URLs being watched. The URL in the event is the URL to the directory from which the volume was unmounted. You will receive one of these notifications for every volume unmount event inside the kernel. This is not a substitute for the notifications provided by the DiskArbitration framework; you only get notified after the unmount has occurred. Beware that unmounting a volume could uncover an arbitrarily large directory hierarchy, although Mac OS X never does that.

Discussion

The flags of the event.

The flags of the event as returned by FSEvents.

Discussion

The event identifier.

The event identifier as returned by FSEvents.

Discussion

Wheter the 64-bit event identifier counter has wrapped around.

Wheter the 64-bit event identifier counter has wrapped around. As a result, previously-issued event identifiers are no longer valid arguments for the sinceEventIdentifier parameter of the CDEvents init methods.

Discussion

Wheter there was some change in the directory at the specific path supplied in this event.

Discussion

Denotes a sentinel event sent to mark the end of the “historical” events sent.

Denotes a sentinel event sent to mark the end of the “historical” events sent as a result of specifying a sinceEventIdentifier argument other than kCDEventsSinceEventNow with the CDEvents init methods.

Discussion

Provides some information as to what might have caused the need to rescan the URL including its children.

Discussion

Denotes a special event sent when there is a change to one of the URLs you asked to watch.

Denotes a special event sent when there is a change to one of the URLs you asked to watch. When this method returns YES, the event identifier is zero and the URL corresponds to one of the URLs you asked to watch (specifically, the one that changed). The URL may no longer exist because it or one of its parents was deleted or renamed. Events with this flag set will only be sent if you passed the flag kFSEventStreamCreateFlagWatchRoot to the CDEvents.

Discussion

Provides some information as to what might have caused the need to rescan the URL including its children.

Discussion

Wheter you must rescan the whole URL including its children.

Wheter your application must rescan not just the URL given in the event, but all its children, recursively. This can happen if there was a problem whereby events were coalesced hierarchically. For example, an event in /Users/jsmith/Music and an event in /Users/jsmith/Pictures might be coalesced into an event with this flag set and URL=/Users/jsmith. If this flag is set you may be able to get an idea of whether the bottleneck happened in the kernel (less likely) or in your client (more likely) by checking if flagUserDropped or flagKernelDropped returns YES.

Discussion

Returns an CDEvent created with the given identifier, date, URL and flags.

Discussion

Returns an CDEvent object initialized with the given identifier, date, URL and flags.