/*! * * Wijmo Library 5.20251.40 * https://developer.mescius.com/wijmo * * Copyright(c) MESCIUS inc. All rights reserved. * * Licensed under the End-User License Agreement For MESCIUS Wijmo Software. * us.sales@mescius.com * https://developer.mescius.com/wijmo/licensing * */ /** * {@module wijmo.angular2.input} * Contains Angular 2 components for the wijmo.input module. * * wijmo.angular2.input is an external TypeScript module that can be imported to your code * using its ambient module name. For example: * * 
import * as wjInput from 'wijmo/wijmo.angular2.input';
*  
* @Component({
*     directives: [wjInput.WjInputNumber],
*     template: '<wj-input-number [(value)]="amount"></wj-input-number>',
*     selector: 'my-cmp',
* })
* export class MyCmp {
*     amount = 0;
* }
* */ /** * */ export declare var ___keepComment: any; import { EventEmitter, AfterViewInit, ElementRef, Injector, ViewContainerRef, TemplateRef, OnInit, OnChanges, OnDestroy, AfterContentInit, ChangeDetectorRef } from '@angular/core'; import { IWjComponentMetadata, IWjComponentMeta, IWjDirectiveMeta } from 'wijmo/wijmo.angular2.directiveBase'; import * as ngCore from '@angular/core'; import * as wjcCore from 'wijmo/wijmo'; import * as wjcInput from 'wijmo/wijmo.input'; declare var wjListBoxMeta: IWjComponentMeta; export { wjListBoxMeta }; /** * Angular 2 component for the {@link wijmo.input.ListBox} control. * * Use the wj-list-box component to add ListBox controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjListBox component is derived from the ListBox control and * inherits all its properties, events and methods. * * The wj-list-box component may contain a {@link wijmo.angular2.input.WjItemTemplate} child directive. */ export declare class WjListBox extends wjcInput.ListBox implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'selectedValue'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo formatItem event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional formatItem Wijmo event name. */ formatItemNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo itemsChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional itemsChanged Wijmo event name. */ itemsChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo itemChecked event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional itemChecked Wijmo event name. */ itemCheckedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo selectedIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional selectedIndexChanged Wijmo event name. */ selectedIndexChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the selectedIndex property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedIndexChange event name. */ selectedIndexChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedItem property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedItemChange event name. */ selectedItemChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedValue property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedValueChange event name. */ selectedValueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo checkedItemsChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional checkedItemsChanged Wijmo event name. */ checkedItemsChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the checkedItems property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the checkedItemsChange event name. */ checkedItemsChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjMultiSelectListBoxMeta: IWjComponentMeta; export { wjMultiSelectListBoxMeta }; /** * Angular 2 component for the {@link wijmo.input.MultiSelectListBox} control. * * Use the wj-multi-select-list-box component to add MultiSelectListBox controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjMultiSelectListBox component is derived from the MultiSelectListBox control and * inherits all its properties, events and methods. */ export declare class WjMultiSelectListBox extends wjcInput.MultiSelectListBox implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'checkedItems'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo checkedItemsChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional checkedItemsChanged Wijmo event name. */ checkedItemsChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the checkedItems property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the checkedItemsChange event name. */ checkedItemsChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo selectedIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional selectedIndexChanged Wijmo event name. */ selectedIndexChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the selectedIndex property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedIndexChange event name. */ selectedIndexChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjComboBoxMeta: IWjComponentMeta; export { wjComboBoxMeta }; /** * Angular 2 component for the {@link wijmo.input.ComboBox} control. * * Use the wj-combo-box component to add ComboBox controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjComboBox component is derived from the ComboBox control and * inherits all its properties, events and methods. * * The wj-combo-box component may contain a {@link wijmo.angular2.input.WjItemTemplate} child directive. */ export declare class WjComboBox extends wjcInput.ComboBox implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'selectedValue'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo itemsSourceChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional itemsSourceChanged Wijmo event name. */ itemsSourceChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo formatItem event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional formatItem Wijmo event name. */ formatItemNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo selectedIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional selectedIndexChanged Wijmo event name. */ selectedIndexChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the selectedIndex property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedIndexChange event name. */ selectedIndexChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedItem property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedItemChange event name. */ selectedItemChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedValue property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedValueChange event name. */ selectedValueChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjAutoCompleteMeta: IWjComponentMeta; export { wjAutoCompleteMeta }; /** * Angular 2 component for the {@link wijmo.input.AutoComplete} control. * * Use the wj-auto-complete component to add AutoComplete controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjAutoComplete component is derived from the AutoComplete control and * inherits all its properties, events and methods. */ export declare class WjAutoComplete extends wjcInput.AutoComplete implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'selectedValue'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo itemsSourceChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional itemsSourceChanged Wijmo event name. */ itemsSourceChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo formatItem event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional formatItem Wijmo event name. */ formatItemNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo selectedIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional selectedIndexChanged Wijmo event name. */ selectedIndexChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the selectedIndex property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedIndexChange event name. */ selectedIndexChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedItem property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedItemChange event name. */ selectedItemChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedValue property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedValueChange event name. */ selectedValueChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjCalendarMeta: IWjComponentMeta; export { wjCalendarMeta }; /** * Angular 2 component for the {@link wijmo.input.Calendar} control. * * Use the wj-calendar component to add Calendar controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjCalendar component is derived from the Calendar control and * inherits all its properties, events and methods. */ export declare class WjCalendar extends wjcInput.Calendar implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'value'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo valueChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional valueChanged Wijmo event name. */ valueChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo rangeEndChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional rangeEndChanged Wijmo event name. */ rangeEndChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the rangeEnd property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the rangeEndChange event name. */ rangeEndChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo rangeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional rangeChanged Wijmo event name. */ rangeChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo displayMonthChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional displayMonthChanged Wijmo event name. */ displayMonthChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the displayMonth property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the displayMonthChange event name. */ displayMonthChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo formatItem event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional formatItem Wijmo event name. */ formatItemNg: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjColorPickerMeta: IWjComponentMeta; export { wjColorPickerMeta }; /** * Angular 2 component for the {@link wijmo.input.ColorPicker} control. * * Use the wj-color-picker component to add ColorPicker controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjColorPicker component is derived from the ColorPicker control and * inherits all its properties, events and methods. */ export declare class WjColorPicker extends wjcInput.ColorPicker implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'value'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo valueChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional valueChanged Wijmo event name. */ valueChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjInputMaskMeta: IWjComponentMeta; export { wjInputMaskMeta }; /** * Angular 2 component for the {@link wijmo.input.InputMask} control. * * Use the wj-input-mask component to add InputMask controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjInputMask component is derived from the InputMask control and * inherits all its properties, events and methods. */ export declare class WjInputMask extends wjcInput.InputMask implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'value'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo valueChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional valueChanged Wijmo event name. */ valueChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the rawValue property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the rawValueChange event name. */ rawValueChangePC: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjInputColorMeta: IWjComponentMeta; export { wjInputColorMeta }; /** * Angular 2 component for the {@link wijmo.input.InputColor} control. * * Use the wj-input-color component to add InputColor controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjInputColor component is derived from the InputColor control and * inherits all its properties, events and methods. */ export declare class WjInputColor extends wjcInput.InputColor implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'value'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo valueChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional valueChanged Wijmo event name. */ valueChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjMultiSelectMeta: IWjComponentMeta; export { wjMultiSelectMeta }; /** * Angular 2 component for the {@link wijmo.input.MultiSelect} control. * * Use the wj-multi-select component to add MultiSelect controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjMultiSelect component is derived from the MultiSelect control and * inherits all its properties, events and methods. * * The wj-multi-select component may contain a {@link wijmo.angular2.input.WjItemTemplate} child directive. */ export declare class WjMultiSelect extends wjcInput.MultiSelect implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'checkedItems'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo itemsSourceChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional itemsSourceChanged Wijmo event name. */ itemsSourceChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo formatItem event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional formatItem Wijmo event name. */ formatItemNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo selectedIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional selectedIndexChanged Wijmo event name. */ selectedIndexChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the selectedIndex property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedIndexChange event name. */ selectedIndexChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedItem property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedItemChange event name. */ selectedItemChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedValue property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedValueChange event name. */ selectedValueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo checkedItemsChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional checkedItemsChanged Wijmo event name. */ checkedItemsChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the checkedItems property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the checkedItemsChange event name. */ checkedItemsChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjMultiAutoCompleteMeta: IWjComponentMeta; export { wjMultiAutoCompleteMeta }; /** * Angular 2 component for the {@link wijmo.input.MultiAutoComplete} control. * * Use the wj-multi-auto-complete component to add MultiAutoComplete controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjMultiAutoComplete component is derived from the MultiAutoComplete control and * inherits all its properties, events and methods. */ export declare class WjMultiAutoComplete extends wjcInput.MultiAutoComplete implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'selectedItems'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo itemsSourceChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional itemsSourceChanged Wijmo event name. */ itemsSourceChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo formatItem event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional formatItem Wijmo event name. */ formatItemNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo selectedIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional selectedIndexChanged Wijmo event name. */ selectedIndexChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the selectedIndex property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedIndexChange event name. */ selectedIndexChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedItem property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedItemChange event name. */ selectedItemChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedValue property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedValueChange event name. */ selectedValueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo selectedItemsChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional selectedItemsChanged Wijmo event name. */ selectedItemsChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the selectedItems property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedItemsChange event name. */ selectedItemsChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjInputNumberMeta: IWjComponentMeta; export { wjInputNumberMeta }; /** * Angular 2 component for the {@link wijmo.input.InputNumber} control. * * Use the wj-input-number component to add InputNumber controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjInputNumber component is derived from the InputNumber control and * inherits all its properties, events and methods. */ export declare class WjInputNumber extends wjcInput.InputNumber implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'value'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo valueChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional valueChanged Wijmo event name. */ valueChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjInputDateMeta: IWjComponentMeta; export { wjInputDateMeta }; /** * Angular 2 component for the {@link wijmo.input.InputDate} control. * * Use the wj-input-date component to add InputDate controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjInputDate component is derived from the InputDate control and * inherits all its properties, events and methods. */ export declare class WjInputDate extends wjcInput.InputDate implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'value'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo valueChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional valueChanged Wijmo event name. */ valueChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo rangeEndChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional rangeEndChanged Wijmo event name. */ rangeEndChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the rangeEnd property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the rangeEndChange event name. */ rangeEndChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo rangeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional rangeChanged Wijmo event name. */ rangeChangedNg: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjInputTimeMeta: IWjComponentMeta; export { wjInputTimeMeta }; /** * Angular 2 component for the {@link wijmo.input.InputTime} control. * * Use the wj-input-time component to add InputTime controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjInputTime component is derived from the InputTime control and * inherits all its properties, events and methods. */ export declare class WjInputTime extends wjcInput.InputTime implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'value'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo itemsSourceChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional itemsSourceChanged Wijmo event name. */ itemsSourceChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo formatItem event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional formatItem Wijmo event name. */ formatItemNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo selectedIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional selectedIndexChanged Wijmo event name. */ selectedIndexChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the selectedIndex property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedIndexChange event name. */ selectedIndexChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedItem property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedItemChange event name. */ selectedItemChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedValue property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedValueChange event name. */ selectedValueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo valueChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional valueChanged Wijmo event name. */ valueChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjInputDateTimeMeta: IWjComponentMeta; export { wjInputDateTimeMeta }; /** * Angular 2 component for the {@link wijmo.input.InputDateTime} control. * * Use the wj-input-date-time component to add InputDateTime controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjInputDateTime component is derived from the InputDateTime control and * inherits all its properties, events and methods. */ export declare class WjInputDateTime extends wjcInput.InputDateTime implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'value'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo valueChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional valueChanged Wijmo event name. */ valueChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo rangeEndChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional rangeEndChanged Wijmo event name. */ rangeEndChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the rangeEnd property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the rangeEndChange event name. */ rangeEndChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo rangeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional rangeChanged Wijmo event name. */ rangeChangedNg: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjInputDateRangeMeta: IWjComponentMeta; export { wjInputDateRangeMeta }; /** * Angular 2 component for the {@link wijmo.input.InputDateRange} control. * * Use the wj-input-date-range component to add InputDateRange controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjInputDateRange component is derived from the InputDateRange control and * inherits all its properties, events and methods. */ export declare class WjInputDateRange extends wjcInput.InputDateRange implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'value'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo valueChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional valueChanged Wijmo event name. */ valueChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo rangeEndChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional rangeEndChanged Wijmo event name. */ rangeEndChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the rangeEnd property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the rangeEndChange event name. */ rangeEndChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo rangeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional rangeChanged Wijmo event name. */ rangeChangedNg: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjMenuMeta: IWjComponentMeta; export { wjMenuMeta }; /** * Angular 2 component for the {@link wijmo.input.Menu} control. * * Use the wj-menu component to add Menu controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjMenu component is derived from the Menu control and * inherits all its properties, events and methods. * * The wj-menu component may contain the following child components: * {@link wijmo.angular2.input.WjMenuItem} * , {@link wijmo.angular2.input.WjMenuSeparator} * and {@link wijmo.angular2.input.WjItemTemplate}. */ export declare class WjMenu extends wjcInput.Menu implements OnInit, OnDestroy, AfterViewInit, OnChanges, AfterContentInit { private _value; private _definedHeader; static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is 'selectedValue'. */ wjModelProperty: string; /** * Allows you to override the global WjOptions.asyncBindings setting for this specific component. * See the WjOptions.{@link WjOptions.asyncBindings} property description for details. */ asyncBindings: boolean; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanging Wijmo event name. */ isDroppedDownChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo isDroppedDownChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional isDroppedDownChanged Wijmo event name. */ isDroppedDownChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the isDroppedDown property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the isDroppedDownChange event name. */ isDroppedDownChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo textChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional textChanged Wijmo event name. */ textChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the text property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the textChange event name. */ textChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo itemsSourceChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional itemsSourceChanged Wijmo event name. */ itemsSourceChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo formatItem event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional formatItem Wijmo event name. */ formatItemNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo selectedIndexChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional selectedIndexChanged Wijmo event name. */ selectedIndexChangedNg: EventEmitter; /** * This event is used to implement two-way binding to the selectedIndex property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedIndexChange event name. */ selectedIndexChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedItem property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedItemChange event name. */ selectedItemChangePC: EventEmitter; /** * This event is used to implement two-way binding to the selectedValue property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the selectedValueChange event name. */ selectedValueChangePC: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo itemClicked event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional itemClicked Wijmo event name. */ itemClickedNg: EventEmitter; /** * This event is used to implement two-way binding to the value property. * It's triggered when the property value changes, with the event argument holding the new property value. * You can bind handlers to this event in templates using the valueChange event name. */ valueChangePC: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; value: any; ngOnChanges(changes: { [key: string]: ngCore.SimpleChange; }): void; ngAfterContentInit(): void; onItemClicked(e?: wjcCore.EventArgs): void; refresh(fullUpdate?: boolean): void; private _attachToControl; private _loadingItems; private _fmtItem; private _updateHeader; } declare var wjMenuItemMeta: IWjComponentMeta; export { wjMenuItemMeta }; /** * Angular 2 directive for {@link wijmo.angular2.input.WjMenu} items. * * The wj-menu-item component must be * contained in a {@link wijmo.angular2.input.WjMenu} component. * * Use the wj-menu-item component to add controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. */ export declare class WjMenuItem implements OnInit, OnDestroy, AfterViewInit { private viewContainerRef; value: any; cmd: any; cmdParam: any; header: string; _ownerMenu: wjcInput.Menu; templateDir: WjMenuItemTemplateDir; contentRoot: HTMLElement; static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Gets or sets a name of a property that this component is assigned to. * Default value is 'itemsSource'. */ wjProperty: string; constructor(elRef: ElementRef, injector: Injector, parentCmp: any, viewContainerRef: ViewContainerRef); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; added(toItem: HTMLElement): void; } export declare class WjMenuItemTemplateDir implements ngCore.AfterContentInit { viewContainerRef: ViewContainerRef; templateRef: TemplateRef; elRef: ElementRef; wjMenuItemTemplateDir: any; ownerItem: WjMenuItem; contentRoot: HTMLElement; constructor(viewContainerRef: ViewContainerRef, templateRef: TemplateRef, elRef: ElementRef, injector: Injector, menuItem: WjMenuItem, menuSeparator: WjMenuSeparator); ngAfterContentInit(): void; } declare var wjMenuSeparatorMeta: IWjComponentMeta; export { wjMenuSeparatorMeta }; /** * Angular 2 directive for {@link wijmo.angular2.input.WjMenu} item separators. * * The wj-menu-separator component must be * contained in a {@link wijmo.angular2.input.WjMenu} component. * * Use the wj-menu-separator component to add controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. */ export declare class WjMenuSeparator extends WjMenuItem implements OnInit, OnDestroy, AfterViewInit { constructor(elRef: ElementRef, injector: Injector, parentCmp: any, viewContainerRef: ViewContainerRef); added(toItem: HTMLElement): void; } declare var wjItemTemplateMeta: IWjDirectiveMeta; export { wjItemTemplateMeta }; /** * Angular 2 directive for item templates of item list components. * * The [wjItemTemplate] directive must be * contained in one of the following components: * {@link wijmo.angular2.input.WjListBox} * , {@link wijmo.angular2.input.WjMenu} * , {@link wijmo.angular2.input.WjComboBox} * or {@link wijmo.angular2.input.WjMultiSelect}. * * The [wjItemTemplate] directive defines a template for items of a component * that it's nested in. * The template may contain an arbitrary HTML fragment with Angular 2 bindings and directives. * The local item, itemIndex and control template variables can be used in Angular 2 * bindings that refer to the data item, its index, and the owner control. For example: * *
<wj-list-box style="max-height:300px;width:250px;"
 *             [itemsSource]="musicians">
 *   <ng-template wjItemTemplate let-item="item" let-itemIndex="itemIndex">
 *       {​{itemIndex + 1}}. <b>{​{item.name}}</b>
 *       <div *ngIf="item.photo">
 *           <img [src]="item.photo" height="100" />
 *           <br />
 *           <a href="https://www.google.com/#newwindow=1&q=The+Beatles+"
 *              target="_blank"
 *              style="color:red">go there!</a>
 *       </div>
 *   </ng-template>
 * </wj-list-box>
*/ export declare class WjItemTemplate implements OnInit, OnDestroy, AfterViewInit { viewContainerRef: ViewContainerRef; templateRef: TemplateRef; wjItemTemplate: any; ownerControl: wjcCore.Control; listBox: wjcInput.ListBox; private _cdRef; static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any, viewContainerRef: ViewContainerRef, templateRef: TemplateRef, cdRef: ChangeDetectorRef); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; private _attachToControl; private _loadingItems; private _fmtItem; private _instantiateTemplate; private static _getListBox; } declare var wjPopupMeta: IWjComponentMeta; export { wjPopupMeta }; /** * Angular 2 component for the {@link wijmo.input.Popup} control. * * Use the wj-popup component to add Popup controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjPopup component is derived from the Popup control and * inherits all its properties, events and methods. */ export declare class WjPopup extends wjcInput.Popup implements OnInit, OnDestroy, AfterViewInit, OnChanges { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is ''. */ wjModelProperty: string; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo showing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional showing Wijmo event name. */ showingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo shown event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional shown Wijmo event name. */ shownNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo hiding event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional hiding Wijmo event name. */ hidingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo hidden event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional hidden Wijmo event name. */ hiddenNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo resizing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional resizing Wijmo event name. */ resizingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo sizeChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional sizeChanging Wijmo event name. */ sizeChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo sizeChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional sizeChanged Wijmo event name. */ sizeChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo resized event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional resized Wijmo event name. */ resizedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo dragging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional dragging Wijmo event name. */ draggingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo positionChanging event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional positionChanging Wijmo event name. */ positionChangingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo positionChanged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional positionChanged Wijmo event name. */ positionChangedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo dragged event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional dragged Wijmo event name. */ draggedNg: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; ngOnChanges(changes: { [key: string]: ngCore.SimpleChange; }): void; dispose(): void; } /** * Angular 2 directive for context menus. * * Use the wjContextMenu directive to add context menus to elements * on the page. The wjContextMenu directive is based on the wj-menu * component; it displays a popup menu when the user performs a context menu * request on an element (usually a right-click). * * The wjContextMenu directive is specified as a parameter added to the * element that the context menu applies to. The parameter value is a * reference to the wj-menu component. For example: * * 
<!-- paragraph with a context menu -->
    *<p [wjContextMenu]="menu" >
    *  This paragraph has a context menu.</p>
    *
    *<!-- define the context menu (hidden and with an id) -->
    *<wj-menu #menu style="display:none">
    *  <wj-menu-item [cmd]="cmdOpen" [cmdParam] ="1">Open...</wj-menu-item>
    *  <wj-menu-item [cmd]="cmdSave" [cmdParam]="2">Save </wj-menu-item>
    *  <wj-menu-item [cmd]="cmdSave" [cmdParam]="3">Save As...</wj-menu-item>
    *  <wj-menu-item [cmd]="cmdNew" [cmdParam] ="4">New...</wj-menu-item>
    *  <wj-menu-separator></wj-menu-separator>
    *  <wj-menu-item [cmd]="cmdExit" [cmdParam]="5">Exit</wj-menu-item>
    *</wj-menu >
*/ export declare class WjContextMenu { private elRef; wjContextMenu: wjcInput.Menu; constructor(elRef: ElementRef); onContextMenu(e: MouseEvent): void; } declare var wjCollectionViewNavigatorMeta: IWjComponentMeta; export { wjCollectionViewNavigatorMeta }; /** * Angular 2 component for the {@link wijmo.input.CollectionViewNavigator} control. * * Use the wj-collection-view-navigator component to add CollectionViewNavigator controls to your * Angular 2 applications. For details about Angular 2 markup syntax, see * Angular 2 Markup. * * The WjCollectionViewNavigator component is derived from the CollectionViewNavigator control and * inherits all its properties, events and methods. */ export declare class WjCollectionViewNavigator extends wjcInput.CollectionViewNavigator implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is ''. */ wjModelProperty: string; /** * Angular (EventEmitter) version of the Wijmo gotFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional gotFocus Wijmo event name. */ gotFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo lostFocus event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional lostFocus Wijmo event name. */ lostFocusNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshing event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshing Wijmo event name. */ refreshingNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo refreshed event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional refreshed Wijmo event name. */ refreshedNg: EventEmitter; /** * Angular (EventEmitter) version of the Wijmo invalidInput event for programmatic access. * Use this event name if you want to subscribe to the Angular version of the event in code. * In template bindings use the conventional invalidInput Wijmo event name. */ invalidInputNg: EventEmitter; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } declare var wjCollectionViewPagerMeta: IWjComponentMeta; export { wjCollectionViewPagerMeta }; /** * Obsolete. Use wj-collection-view-navigator with [byPage]="true" instead. * * Angular 2 component for an {@link ICollectionView} pager element. * * Use the wj-collection-view-pager component to add an element * that allows users to navigate through the pages in a paged {@link ICollectionView}. * For details about Angular 2 markup syntax, see * Angular 2 Markup. For example: * * 
<wj-collection-view-pager
    *   [cv]="myCollectionView">
    * </wj-collection-view-pager>
*/ export declare class WjCollectionViewPager extends wjcInput.CollectionViewNavigator implements OnInit, OnDestroy, AfterViewInit { static readonly meta: IWjComponentMetadata; private _wjBehaviour; /** * Indicates whether the component has been initialized by Angular. * Changes its value from false to true right before triggering the initialized event. */ isInitialized: boolean; /** * This event is triggered after the component has been initialized by Angular, that is * all bound properties have been assigned and child components (if any) have been initialized. */ initialized: EventEmitter; /** * Defines a name of a property represented by [(ngModel)] directive (if specified). * Default value is ''. */ wjModelProperty: string; constructor(elRef: ElementRef, injector: Injector, parentCmp: any); /** * If you create a custom component inherited from a Wijmo component, you can override this * method and perform necessary initializations that you usually do in a class constructor. * This method is called in the last line of a Wijmo component constructor and allows you * to not declare your custom component's constructor at all, thus preventing you from a necessity * to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters. */ created(): void; ngOnInit(): void; ngAfterViewInit(): void; ngOnDestroy(): void; addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void; } export declare class WjInputModule { }