Properties
ContentImage
#Gets or sets the content image of the notification
Remarks: This is used to provide context to the user for what the notification is for.
Remarks: Some platforms may use this to identify controls (e.g. web)
NativeHandle
nint NativeHandle { get; }
Gets the native platform-specific handle for integration purposes
Value: The native handle.
RequiresTrayIndicator
#Gets a value indicating whether this Notification requires a TrayIndicator to be displayed.
UserData
#Gets or sets user data for the notification.
Remarks: Use this to store application-specific data that would be useful for knowing what caused the notification. The data you store would usually determine what action to perform in the application. This is returned via Application.NotificationActivated via the NotificationEventArgs.
Methods
Remarks: Most events are late bound by this method. Instead of wiring all events, this will be called with an event string that is defined by the control. This is called automatically when attaching to events, but must be called manually when users of the control only override the event's On... method.
Initialize
void Initialize()
Called after the widget is constructed
Remarks: This gets called automatically after the control is constructed and the Widget.IHandler.Widget and Widget.Platform properties are set. When the handler has specialized construction methods, then the AutoInitializeAttribute can be used to disable automatic initialization. In this case, it is the responsibility of the subclass to call Widget.Initialize()
Show
#Shows the current notification.
Parameters:
| indicator (TrayIndicator = null) | Indicator to use to show the notification. |
UnhandleEvent
Called when the last subscriber to an event has been removed, so the platform can stop listening for it.
Remarks: Only reached for events whose remove accessor uses PropertyStore.RemoveHandlerEvent(string, Delegate), and only for events that were attached because something subscribed to them. An event attached because the widget overrides its On[Event] method is never detached, since it has to keep firing regardless. Most events stay attached for the life of the widget, which costs nothing. Detaching is worth wiring up for the few that hold onto something expensive or process wide while they are attached, such as a system wide hook. Handlers deriving from WidgetHandler<TWidget> get an implementation of this that dispatches to WidgetHandler<TWidget>.DetachEvent(string), which is what to override.
Parameters:
| id (string) | ID of the event to stop handling |