StorageItemQueryResult.ContentsChanged Event

Definition

Namespace:

Windows.Storage.Search

Fires when an item is added to, deleted from, or modified in the folder being queried. This event only fires after GetItemsAsync has been called at least once.

// Register
event_token ContentsChanged(TypedEventHandler<IStorageQueryResultBase, IInspectable const&> const& handler) const;

// Revoke with event_token
void ContentsChanged(event_token const* cookie) const;

// Revoke with event_revoker
StorageItemQueryResult::ContentsChanged_revoker ContentsChanged(auto_revoke_t, TypedEventHandler<IStorageQueryResultBase, IInspectable const&> const& handler) const;

public event TypedEventHandler<IStorageQueryResultBase,object> ContentsChanged;

function onContentsChanged(eventArgs) { /* Your code */ }
storageItemQueryResult.addEventListener("contentschanged", onContentsChanged);
storageItemQueryResult.removeEventListener("contentschanged", onContentsChanged);
- or -
storageItemQueryResult.oncontentschanged = onContentsChanged;

Public Custom Event ContentsChanged As TypedEventHandler(Of IStorageQueryResultBase, Object) Implements ContentsChanged

Event Type

TypedEventHandler<IStorageQueryResultBase,Object>

TypedEventHandler<IStorageQueryResultBase,IInspectable>

Implements

ContentsChanged

Remarks

If you register a handler for this event, keep that handler registered while you suspend your app (in response to oncheckpoint or Suspending). Your app will not receive ContentsChanged events while it is suspended and when your app resumes it will receive a single event that aggregates all of the changes if any occurred.

Additionally, keep in mind that registering and removing event handlers are synchronous operations and might cause your app to stop responding briefly if you execute them on your app's UI thread. Wherever possible, use a thread other than your app's UI thread to register and unregister these event handlers.