WebAccountMonitor.AccountPictureUpdated Event

// Register
event_token AccountPictureUpdated(TypedEventHandler<WebAccountMonitor, WebAccountEventArgs const&> const& handler) const;

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

// Revoke with event_revoker
WebAccountMonitor::AccountPictureUpdated_revoker AccountPictureUpdated(auto_revoke_t, TypedEventHandler<WebAccountMonitor, WebAccountEventArgs const&> const& handler) const;

public event TypedEventHandler<WebAccountMonitor,WebAccountEventArgs> AccountPictureUpdated;

function onAccountPictureUpdated(eventArgs) { /* Your code */ }
webAccountMonitor.addEventListener("accountpictureupdated", onAccountPictureUpdated);
webAccountMonitor.removeEventListener("accountpictureupdated", onAccountPictureUpdated);
- or -
webAccountMonitor.onaccountpictureupdated = onAccountPictureUpdated;

Public Custom Event AccountPictureUpdated As TypedEventHandler(Of WebAccountMonitor, WebAccountEventArgs) 

Event Type

Windows requirements

Remarks

When a picture is updated, WAM will fire both the Updated and AccountPictureUpdated events so that users who were tracking picture updates by listening to Updated event wont regress.

A new Boolean property “IsPictureUpdated” exists in the payload of the events that allows callers listening only to AccountUpdated events to differentiate between a picuture update and a normal account update.

Applies to

See also

• Updated