Properties
Collate
#Gets or sets a value indicating whether to collate the copies.
Remarks: When
true, all pages of the document will be printed together for each copy. e.g. 123, 123, 123. When false, each page will print all copies together, e.g. 111, 222, 333.Value:
true if collate; otherwise, false.Remarks: Some platforms may use this to identify controls (e.g. web)
MaximumPageRange
#Gets or sets the maximum page range the user can select.
Value: The maximum page range.
NativeHandle
nint NativeHandle { get; }
Gets the native platform-specific handle for integration purposes
Value: The native handle.
Reverse
#Gets or sets a value indicating whether to print in reverse.
Remarks: Printing in reverse will typically finish the job with the first page of the document at the top, since most printers stack the pages from bottom to top. Each platform can have a different default for this, depending on the system settings or usual defaults of other applications.
Value:
true to print in reverse; otherwise, false.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()
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 |