@mescius/wijmo.angular2legacy.input 5.20232.939
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/COMMERCIAL-LICENSE.html +485 -0
- package/README.md +363 -0
- package/es2015-commonjs.js +14 -0
- package/es2015-esm.js +14 -0
- package/es5-esm.js +14 -0
- package/index.d.ts +2627 -0
- package/index.js +14 -0
- package/index.metadata.json +1 -0
- package/package.json +46 -0
package/index.d.ts
ADDED
|
@@ -0,0 +1,2627 @@
|
|
|
1
|
+
/*!
|
|
2
|
+
*
|
|
3
|
+
* Wijmo Library 5.20232.939
|
|
4
|
+
* https://developer.mescius.com/wijmo
|
|
5
|
+
*
|
|
6
|
+
* Copyright(c) MESCIUS inc. All rights reserved.
|
|
7
|
+
*
|
|
8
|
+
* Licensed under the End-User License Agreement For MESCIUS Wijmo Software.
|
|
9
|
+
* us.sales@mescius.com
|
|
10
|
+
* https://developer.mescius.com/wijmo/licensing
|
|
11
|
+
*
|
|
12
|
+
*/
|
|
13
|
+
/**
|
|
14
|
+
* {@module wijmo.angular2legacy.input}
|
|
15
|
+
* Contains Angular 2 components for the <b>wijmo.input</b> module.
|
|
16
|
+
*
|
|
17
|
+
* <b>wijmo.angular2legacy.input</b> is an external TypeScript module that can be imported to your code
|
|
18
|
+
* using its ambient module name. For example:
|
|
19
|
+
*
|
|
20
|
+
* <pre>import * as wjInput from 'wijmo/wijmo.angular2legacy.input';
|
|
21
|
+
*
|
|
22
|
+
* @Component({
|
|
23
|
+
* directives: [wjInput.WjInputNumber],
|
|
24
|
+
* template: '<wj-input-number [(value)]="amount"></wj-input-number>',
|
|
25
|
+
* selector: 'my-cmp',
|
|
26
|
+
* })
|
|
27
|
+
* export class MyCmp {
|
|
28
|
+
* amount = 0;
|
|
29
|
+
* }</pre>
|
|
30
|
+
*
|
|
31
|
+
*/
|
|
32
|
+
/**
|
|
33
|
+
*
|
|
34
|
+
*/
|
|
35
|
+
export declare var ___keepComment: any;
|
|
36
|
+
import { EventEmitter, AfterViewInit, ElementRef, Injector, ViewContainerRef, TemplateRef, OnInit, OnChanges, OnDestroy, AfterContentInit, ChangeDetectorRef } from '@angular/core';
|
|
37
|
+
import { IWjComponentMetadata, IWjComponentMeta, IWjDirectiveMeta } from '@grapecity/wijmo.angular2legacy.directivebase';
|
|
38
|
+
import * as ngCore from '@angular/core';
|
|
39
|
+
import * as wjcCore from '@grapecity/wijmo';
|
|
40
|
+
import * as wjcInput from '@grapecity/wijmo.input';
|
|
41
|
+
declare var wjListBoxMeta: IWjComponentMeta;
|
|
42
|
+
export { wjListBoxMeta };
|
|
43
|
+
/**
|
|
44
|
+
* Angular 2 component for the {@link wijmo.input.ListBox} control.
|
|
45
|
+
*
|
|
46
|
+
* Use the <b>wj-list-box</b> component to add <b>ListBox</b> controls to your
|
|
47
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
48
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
49
|
+
*
|
|
50
|
+
* The <b>WjListBox</b> component is derived from the <b>ListBox</b> control and
|
|
51
|
+
* inherits all its properties, events and methods.
|
|
52
|
+
*
|
|
53
|
+
* The <b>wj-list-box</b> component may contain a {@link wijmo.angular2legacy.input.WjItemTemplate} child directive.
|
|
54
|
+
*/
|
|
55
|
+
export declare class WjListBox extends wjcInput.ListBox implements OnInit, OnDestroy, AfterViewInit {
|
|
56
|
+
static readonly meta: IWjComponentMetadata;
|
|
57
|
+
private _wjBehaviour;
|
|
58
|
+
/**
|
|
59
|
+
* Indicates whether the component has been initialized by Angular.
|
|
60
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
61
|
+
*/
|
|
62
|
+
isInitialized: boolean;
|
|
63
|
+
/**
|
|
64
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
65
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
66
|
+
*/
|
|
67
|
+
initialized: EventEmitter<any>;
|
|
68
|
+
/**
|
|
69
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
70
|
+
* Default value is 'selectedValue'.
|
|
71
|
+
*/
|
|
72
|
+
wjModelProperty: string;
|
|
73
|
+
/**
|
|
74
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
75
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
76
|
+
*/
|
|
77
|
+
asyncBindings: boolean;
|
|
78
|
+
/**
|
|
79
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
80
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
81
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
82
|
+
*/
|
|
83
|
+
gotFocusNg: EventEmitter<any>;
|
|
84
|
+
/**
|
|
85
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
86
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
87
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
88
|
+
*/
|
|
89
|
+
lostFocusNg: EventEmitter<any>;
|
|
90
|
+
/**
|
|
91
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
92
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
93
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
94
|
+
*/
|
|
95
|
+
refreshingNg: EventEmitter<any>;
|
|
96
|
+
/**
|
|
97
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
98
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
99
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
100
|
+
*/
|
|
101
|
+
refreshedNg: EventEmitter<any>;
|
|
102
|
+
/**
|
|
103
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
104
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
105
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
106
|
+
*/
|
|
107
|
+
invalidInputNg: EventEmitter<any>;
|
|
108
|
+
/**
|
|
109
|
+
* Angular (EventEmitter) version of the Wijmo <b>formatItem</b> event for programmatic access.
|
|
110
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
111
|
+
* In template bindings use the conventional <b>formatItem</b> Wijmo event name.
|
|
112
|
+
*/
|
|
113
|
+
formatItemNg: EventEmitter<any>;
|
|
114
|
+
/**
|
|
115
|
+
* Angular (EventEmitter) version of the Wijmo <b>itemsChanged</b> event for programmatic access.
|
|
116
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
117
|
+
* In template bindings use the conventional <b>itemsChanged</b> Wijmo event name.
|
|
118
|
+
*/
|
|
119
|
+
itemsChangedNg: EventEmitter<any>;
|
|
120
|
+
/**
|
|
121
|
+
* Angular (EventEmitter) version of the Wijmo <b>itemChecked</b> event for programmatic access.
|
|
122
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
123
|
+
* In template bindings use the conventional <b>itemChecked</b> Wijmo event name.
|
|
124
|
+
*/
|
|
125
|
+
itemCheckedNg: EventEmitter<any>;
|
|
126
|
+
/**
|
|
127
|
+
* Angular (EventEmitter) version of the Wijmo <b>selectedIndexChanged</b> event for programmatic access.
|
|
128
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
129
|
+
* In template bindings use the conventional <b>selectedIndexChanged</b> Wijmo event name.
|
|
130
|
+
*/
|
|
131
|
+
selectedIndexChangedNg: EventEmitter<any>;
|
|
132
|
+
/**
|
|
133
|
+
* This event is used to implement two-way binding to the <b>selectedIndex</b> property.
|
|
134
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
135
|
+
* You can bind handlers to this event in templates using the <b>selectedIndexChange</b> event name.
|
|
136
|
+
*/
|
|
137
|
+
selectedIndexChangePC: EventEmitter<any>;
|
|
138
|
+
/**
|
|
139
|
+
* This event is used to implement two-way binding to the <b>selectedItem</b> property.
|
|
140
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
141
|
+
* You can bind handlers to this event in templates using the <b>selectedItemChange</b> event name.
|
|
142
|
+
*/
|
|
143
|
+
selectedItemChangePC: EventEmitter<any>;
|
|
144
|
+
/**
|
|
145
|
+
* This event is used to implement two-way binding to the <b>selectedValue</b> property.
|
|
146
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
147
|
+
* You can bind handlers to this event in templates using the <b>selectedValueChange</b> event name.
|
|
148
|
+
*/
|
|
149
|
+
selectedValueChangePC: EventEmitter<any>;
|
|
150
|
+
/**
|
|
151
|
+
* Angular (EventEmitter) version of the Wijmo <b>checkedItemsChanged</b> event for programmatic access.
|
|
152
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
153
|
+
* In template bindings use the conventional <b>checkedItemsChanged</b> Wijmo event name.
|
|
154
|
+
*/
|
|
155
|
+
checkedItemsChangedNg: EventEmitter<any>;
|
|
156
|
+
/**
|
|
157
|
+
* This event is used to implement two-way binding to the <b>checkedItems</b> property.
|
|
158
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
159
|
+
* You can bind handlers to this event in templates using the <b>checkedItemsChange</b> event name.
|
|
160
|
+
*/
|
|
161
|
+
checkedItemsChangePC: EventEmitter<any>;
|
|
162
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
163
|
+
/**
|
|
164
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
165
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
166
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
167
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
168
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
169
|
+
*/
|
|
170
|
+
created(): void;
|
|
171
|
+
ngOnInit(): void;
|
|
172
|
+
ngAfterViewInit(): void;
|
|
173
|
+
ngOnDestroy(): void;
|
|
174
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
175
|
+
}
|
|
176
|
+
declare var wjMultiSelectListBoxMeta: IWjComponentMeta;
|
|
177
|
+
export { wjMultiSelectListBoxMeta };
|
|
178
|
+
/**
|
|
179
|
+
* Angular 2 component for the {@link wijmo.input.MultiSelectListBox} control.
|
|
180
|
+
*
|
|
181
|
+
* Use the <b>wj-multi-select-list-box</b> component to add <b>MultiSelectListBox</b> controls to your
|
|
182
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
183
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
184
|
+
*
|
|
185
|
+
* The <b>WjMultiSelectListBox</b> component is derived from the <b>MultiSelectListBox</b> control and
|
|
186
|
+
* inherits all its properties, events and methods.
|
|
187
|
+
*/
|
|
188
|
+
export declare class WjMultiSelectListBox extends wjcInput.MultiSelectListBox implements OnInit, OnDestroy, AfterViewInit {
|
|
189
|
+
static readonly meta: IWjComponentMetadata;
|
|
190
|
+
private _wjBehaviour;
|
|
191
|
+
/**
|
|
192
|
+
* Indicates whether the component has been initialized by Angular.
|
|
193
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
194
|
+
*/
|
|
195
|
+
isInitialized: boolean;
|
|
196
|
+
/**
|
|
197
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
198
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
199
|
+
*/
|
|
200
|
+
initialized: EventEmitter<any>;
|
|
201
|
+
/**
|
|
202
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
203
|
+
* Default value is 'checkedItems'.
|
|
204
|
+
*/
|
|
205
|
+
wjModelProperty: string;
|
|
206
|
+
/**
|
|
207
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
208
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
209
|
+
*/
|
|
210
|
+
asyncBindings: boolean;
|
|
211
|
+
/**
|
|
212
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
213
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
214
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
215
|
+
*/
|
|
216
|
+
gotFocusNg: EventEmitter<any>;
|
|
217
|
+
/**
|
|
218
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
219
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
220
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
221
|
+
*/
|
|
222
|
+
lostFocusNg: EventEmitter<any>;
|
|
223
|
+
/**
|
|
224
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
225
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
226
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
227
|
+
*/
|
|
228
|
+
refreshingNg: EventEmitter<any>;
|
|
229
|
+
/**
|
|
230
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
231
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
232
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
233
|
+
*/
|
|
234
|
+
refreshedNg: EventEmitter<any>;
|
|
235
|
+
/**
|
|
236
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
237
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
238
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
239
|
+
*/
|
|
240
|
+
invalidInputNg: EventEmitter<any>;
|
|
241
|
+
/**
|
|
242
|
+
* Angular (EventEmitter) version of the Wijmo <b>checkedItemsChanged</b> event for programmatic access.
|
|
243
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
244
|
+
* In template bindings use the conventional <b>checkedItemsChanged</b> Wijmo event name.
|
|
245
|
+
*/
|
|
246
|
+
checkedItemsChangedNg: EventEmitter<any>;
|
|
247
|
+
/**
|
|
248
|
+
* This event is used to implement two-way binding to the <b>checkedItems</b> property.
|
|
249
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
250
|
+
* You can bind handlers to this event in templates using the <b>checkedItemsChange</b> event name.
|
|
251
|
+
*/
|
|
252
|
+
checkedItemsChangePC: EventEmitter<any>;
|
|
253
|
+
/**
|
|
254
|
+
* Angular (EventEmitter) version of the Wijmo <b>selectedIndexChanged</b> event for programmatic access.
|
|
255
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
256
|
+
* In template bindings use the conventional <b>selectedIndexChanged</b> Wijmo event name.
|
|
257
|
+
*/
|
|
258
|
+
selectedIndexChangedNg: EventEmitter<any>;
|
|
259
|
+
/**
|
|
260
|
+
* This event is used to implement two-way binding to the <b>selectedIndex</b> property.
|
|
261
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
262
|
+
* You can bind handlers to this event in templates using the <b>selectedIndexChange</b> event name.
|
|
263
|
+
*/
|
|
264
|
+
selectedIndexChangePC: EventEmitter<any>;
|
|
265
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
266
|
+
/**
|
|
267
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
268
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
269
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
270
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
271
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
272
|
+
*/
|
|
273
|
+
created(): void;
|
|
274
|
+
ngOnInit(): void;
|
|
275
|
+
ngAfterViewInit(): void;
|
|
276
|
+
ngOnDestroy(): void;
|
|
277
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
278
|
+
}
|
|
279
|
+
declare var wjComboBoxMeta: IWjComponentMeta;
|
|
280
|
+
export { wjComboBoxMeta };
|
|
281
|
+
/**
|
|
282
|
+
* Angular 2 component for the {@link wijmo.input.ComboBox} control.
|
|
283
|
+
*
|
|
284
|
+
* Use the <b>wj-combo-box</b> component to add <b>ComboBox</b> controls to your
|
|
285
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
286
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
287
|
+
*
|
|
288
|
+
* The <b>WjComboBox</b> component is derived from the <b>ComboBox</b> control and
|
|
289
|
+
* inherits all its properties, events and methods.
|
|
290
|
+
*
|
|
291
|
+
* The <b>wj-combo-box</b> component may contain a {@link wijmo.angular2legacy.input.WjItemTemplate} child directive.
|
|
292
|
+
*/
|
|
293
|
+
export declare class WjComboBox extends wjcInput.ComboBox implements OnInit, OnDestroy, AfterViewInit {
|
|
294
|
+
static readonly meta: IWjComponentMetadata;
|
|
295
|
+
private _wjBehaviour;
|
|
296
|
+
/**
|
|
297
|
+
* Indicates whether the component has been initialized by Angular.
|
|
298
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
299
|
+
*/
|
|
300
|
+
isInitialized: boolean;
|
|
301
|
+
/**
|
|
302
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
303
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
304
|
+
*/
|
|
305
|
+
initialized: EventEmitter<any>;
|
|
306
|
+
/**
|
|
307
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
308
|
+
* Default value is 'selectedValue'.
|
|
309
|
+
*/
|
|
310
|
+
wjModelProperty: string;
|
|
311
|
+
/**
|
|
312
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
313
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
314
|
+
*/
|
|
315
|
+
asyncBindings: boolean;
|
|
316
|
+
/**
|
|
317
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
318
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
319
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
320
|
+
*/
|
|
321
|
+
gotFocusNg: EventEmitter<any>;
|
|
322
|
+
/**
|
|
323
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
324
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
325
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
326
|
+
*/
|
|
327
|
+
lostFocusNg: EventEmitter<any>;
|
|
328
|
+
/**
|
|
329
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
330
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
331
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
332
|
+
*/
|
|
333
|
+
refreshingNg: EventEmitter<any>;
|
|
334
|
+
/**
|
|
335
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
336
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
337
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
338
|
+
*/
|
|
339
|
+
refreshedNg: EventEmitter<any>;
|
|
340
|
+
/**
|
|
341
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
342
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
343
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
344
|
+
*/
|
|
345
|
+
invalidInputNg: EventEmitter<any>;
|
|
346
|
+
/**
|
|
347
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
348
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
349
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
350
|
+
*/
|
|
351
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
352
|
+
/**
|
|
353
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
354
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
355
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
356
|
+
*/
|
|
357
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
358
|
+
/**
|
|
359
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
360
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
361
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
362
|
+
*/
|
|
363
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
364
|
+
/**
|
|
365
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
366
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
367
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
368
|
+
*/
|
|
369
|
+
textChangedNg: EventEmitter<any>;
|
|
370
|
+
/**
|
|
371
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
372
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
373
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
374
|
+
*/
|
|
375
|
+
textChangePC: EventEmitter<any>;
|
|
376
|
+
/**
|
|
377
|
+
* Angular (EventEmitter) version of the Wijmo <b>itemsSourceChanged</b> event for programmatic access.
|
|
378
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
379
|
+
* In template bindings use the conventional <b>itemsSourceChanged</b> Wijmo event name.
|
|
380
|
+
*/
|
|
381
|
+
itemsSourceChangedNg: EventEmitter<any>;
|
|
382
|
+
/**
|
|
383
|
+
* Angular (EventEmitter) version of the Wijmo <b>formatItem</b> event for programmatic access.
|
|
384
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
385
|
+
* In template bindings use the conventional <b>formatItem</b> Wijmo event name.
|
|
386
|
+
*/
|
|
387
|
+
formatItemNg: EventEmitter<any>;
|
|
388
|
+
/**
|
|
389
|
+
* Angular (EventEmitter) version of the Wijmo <b>selectedIndexChanged</b> event for programmatic access.
|
|
390
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
391
|
+
* In template bindings use the conventional <b>selectedIndexChanged</b> Wijmo event name.
|
|
392
|
+
*/
|
|
393
|
+
selectedIndexChangedNg: EventEmitter<any>;
|
|
394
|
+
/**
|
|
395
|
+
* This event is used to implement two-way binding to the <b>selectedIndex</b> property.
|
|
396
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
397
|
+
* You can bind handlers to this event in templates using the <b>selectedIndexChange</b> event name.
|
|
398
|
+
*/
|
|
399
|
+
selectedIndexChangePC: EventEmitter<any>;
|
|
400
|
+
/**
|
|
401
|
+
* This event is used to implement two-way binding to the <b>selectedItem</b> property.
|
|
402
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
403
|
+
* You can bind handlers to this event in templates using the <b>selectedItemChange</b> event name.
|
|
404
|
+
*/
|
|
405
|
+
selectedItemChangePC: EventEmitter<any>;
|
|
406
|
+
/**
|
|
407
|
+
* This event is used to implement two-way binding to the <b>selectedValue</b> property.
|
|
408
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
409
|
+
* You can bind handlers to this event in templates using the <b>selectedValueChange</b> event name.
|
|
410
|
+
*/
|
|
411
|
+
selectedValueChangePC: EventEmitter<any>;
|
|
412
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
413
|
+
/**
|
|
414
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
415
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
416
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
417
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
418
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
419
|
+
*/
|
|
420
|
+
created(): void;
|
|
421
|
+
ngOnInit(): void;
|
|
422
|
+
ngAfterViewInit(): void;
|
|
423
|
+
ngOnDestroy(): void;
|
|
424
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
425
|
+
}
|
|
426
|
+
declare var wjAutoCompleteMeta: IWjComponentMeta;
|
|
427
|
+
export { wjAutoCompleteMeta };
|
|
428
|
+
/**
|
|
429
|
+
* Angular 2 component for the {@link wijmo.input.AutoComplete} control.
|
|
430
|
+
*
|
|
431
|
+
* Use the <b>wj-auto-complete</b> component to add <b>AutoComplete</b> controls to your
|
|
432
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
433
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
434
|
+
*
|
|
435
|
+
* The <b>WjAutoComplete</b> component is derived from the <b>AutoComplete</b> control and
|
|
436
|
+
* inherits all its properties, events and methods.
|
|
437
|
+
*/
|
|
438
|
+
export declare class WjAutoComplete extends wjcInput.AutoComplete implements OnInit, OnDestroy, AfterViewInit {
|
|
439
|
+
static readonly meta: IWjComponentMetadata;
|
|
440
|
+
private _wjBehaviour;
|
|
441
|
+
/**
|
|
442
|
+
* Indicates whether the component has been initialized by Angular.
|
|
443
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
444
|
+
*/
|
|
445
|
+
isInitialized: boolean;
|
|
446
|
+
/**
|
|
447
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
448
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
449
|
+
*/
|
|
450
|
+
initialized: EventEmitter<any>;
|
|
451
|
+
/**
|
|
452
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
453
|
+
* Default value is 'selectedValue'.
|
|
454
|
+
*/
|
|
455
|
+
wjModelProperty: string;
|
|
456
|
+
/**
|
|
457
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
458
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
459
|
+
*/
|
|
460
|
+
asyncBindings: boolean;
|
|
461
|
+
/**
|
|
462
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
463
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
464
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
465
|
+
*/
|
|
466
|
+
gotFocusNg: EventEmitter<any>;
|
|
467
|
+
/**
|
|
468
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
469
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
470
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
471
|
+
*/
|
|
472
|
+
lostFocusNg: EventEmitter<any>;
|
|
473
|
+
/**
|
|
474
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
475
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
476
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
477
|
+
*/
|
|
478
|
+
refreshingNg: EventEmitter<any>;
|
|
479
|
+
/**
|
|
480
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
481
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
482
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
483
|
+
*/
|
|
484
|
+
refreshedNg: EventEmitter<any>;
|
|
485
|
+
/**
|
|
486
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
487
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
488
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
489
|
+
*/
|
|
490
|
+
invalidInputNg: EventEmitter<any>;
|
|
491
|
+
/**
|
|
492
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
493
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
494
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
495
|
+
*/
|
|
496
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
497
|
+
/**
|
|
498
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
499
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
500
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
501
|
+
*/
|
|
502
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
503
|
+
/**
|
|
504
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
505
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
506
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
507
|
+
*/
|
|
508
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
509
|
+
/**
|
|
510
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
511
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
512
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
513
|
+
*/
|
|
514
|
+
textChangedNg: EventEmitter<any>;
|
|
515
|
+
/**
|
|
516
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
517
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
518
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
519
|
+
*/
|
|
520
|
+
textChangePC: EventEmitter<any>;
|
|
521
|
+
/**
|
|
522
|
+
* Angular (EventEmitter) version of the Wijmo <b>itemsSourceChanged</b> event for programmatic access.
|
|
523
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
524
|
+
* In template bindings use the conventional <b>itemsSourceChanged</b> Wijmo event name.
|
|
525
|
+
*/
|
|
526
|
+
itemsSourceChangedNg: EventEmitter<any>;
|
|
527
|
+
/**
|
|
528
|
+
* Angular (EventEmitter) version of the Wijmo <b>formatItem</b> event for programmatic access.
|
|
529
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
530
|
+
* In template bindings use the conventional <b>formatItem</b> Wijmo event name.
|
|
531
|
+
*/
|
|
532
|
+
formatItemNg: EventEmitter<any>;
|
|
533
|
+
/**
|
|
534
|
+
* Angular (EventEmitter) version of the Wijmo <b>selectedIndexChanged</b> event for programmatic access.
|
|
535
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
536
|
+
* In template bindings use the conventional <b>selectedIndexChanged</b> Wijmo event name.
|
|
537
|
+
*/
|
|
538
|
+
selectedIndexChangedNg: EventEmitter<any>;
|
|
539
|
+
/**
|
|
540
|
+
* This event is used to implement two-way binding to the <b>selectedIndex</b> property.
|
|
541
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
542
|
+
* You can bind handlers to this event in templates using the <b>selectedIndexChange</b> event name.
|
|
543
|
+
*/
|
|
544
|
+
selectedIndexChangePC: EventEmitter<any>;
|
|
545
|
+
/**
|
|
546
|
+
* This event is used to implement two-way binding to the <b>selectedItem</b> property.
|
|
547
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
548
|
+
* You can bind handlers to this event in templates using the <b>selectedItemChange</b> event name.
|
|
549
|
+
*/
|
|
550
|
+
selectedItemChangePC: EventEmitter<any>;
|
|
551
|
+
/**
|
|
552
|
+
* This event is used to implement two-way binding to the <b>selectedValue</b> property.
|
|
553
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
554
|
+
* You can bind handlers to this event in templates using the <b>selectedValueChange</b> event name.
|
|
555
|
+
*/
|
|
556
|
+
selectedValueChangePC: EventEmitter<any>;
|
|
557
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
558
|
+
/**
|
|
559
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
560
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
561
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
562
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
563
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
564
|
+
*/
|
|
565
|
+
created(): void;
|
|
566
|
+
ngOnInit(): void;
|
|
567
|
+
ngAfterViewInit(): void;
|
|
568
|
+
ngOnDestroy(): void;
|
|
569
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
570
|
+
}
|
|
571
|
+
declare var wjCalendarMeta: IWjComponentMeta;
|
|
572
|
+
export { wjCalendarMeta };
|
|
573
|
+
/**
|
|
574
|
+
* Angular 2 component for the {@link wijmo.input.Calendar} control.
|
|
575
|
+
*
|
|
576
|
+
* Use the <b>wj-calendar</b> component to add <b>Calendar</b> controls to your
|
|
577
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
578
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
579
|
+
*
|
|
580
|
+
* The <b>WjCalendar</b> component is derived from the <b>Calendar</b> control and
|
|
581
|
+
* inherits all its properties, events and methods.
|
|
582
|
+
*/
|
|
583
|
+
export declare class WjCalendar extends wjcInput.Calendar implements OnInit, OnDestroy, AfterViewInit {
|
|
584
|
+
static readonly meta: IWjComponentMetadata;
|
|
585
|
+
private _wjBehaviour;
|
|
586
|
+
/**
|
|
587
|
+
* Indicates whether the component has been initialized by Angular.
|
|
588
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
589
|
+
*/
|
|
590
|
+
isInitialized: boolean;
|
|
591
|
+
/**
|
|
592
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
593
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
594
|
+
*/
|
|
595
|
+
initialized: EventEmitter<any>;
|
|
596
|
+
/**
|
|
597
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
598
|
+
* Default value is 'value'.
|
|
599
|
+
*/
|
|
600
|
+
wjModelProperty: string;
|
|
601
|
+
/**
|
|
602
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
603
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
604
|
+
*/
|
|
605
|
+
asyncBindings: boolean;
|
|
606
|
+
/**
|
|
607
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
608
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
609
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
610
|
+
*/
|
|
611
|
+
gotFocusNg: EventEmitter<any>;
|
|
612
|
+
/**
|
|
613
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
614
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
615
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
616
|
+
*/
|
|
617
|
+
lostFocusNg: EventEmitter<any>;
|
|
618
|
+
/**
|
|
619
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
620
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
621
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
622
|
+
*/
|
|
623
|
+
refreshingNg: EventEmitter<any>;
|
|
624
|
+
/**
|
|
625
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
626
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
627
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
628
|
+
*/
|
|
629
|
+
refreshedNg: EventEmitter<any>;
|
|
630
|
+
/**
|
|
631
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
632
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
633
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
634
|
+
*/
|
|
635
|
+
invalidInputNg: EventEmitter<any>;
|
|
636
|
+
/**
|
|
637
|
+
* Angular (EventEmitter) version of the Wijmo <b>valueChanged</b> event for programmatic access.
|
|
638
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
639
|
+
* In template bindings use the conventional <b>valueChanged</b> Wijmo event name.
|
|
640
|
+
*/
|
|
641
|
+
valueChangedNg: EventEmitter<any>;
|
|
642
|
+
/**
|
|
643
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
644
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
645
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
646
|
+
*/
|
|
647
|
+
valueChangePC: EventEmitter<any>;
|
|
648
|
+
/**
|
|
649
|
+
* Angular (EventEmitter) version of the Wijmo <b>rangeEndChanged</b> event for programmatic access.
|
|
650
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
651
|
+
* In template bindings use the conventional <b>rangeEndChanged</b> Wijmo event name.
|
|
652
|
+
*/
|
|
653
|
+
rangeEndChangedNg: EventEmitter<any>;
|
|
654
|
+
/**
|
|
655
|
+
* This event is used to implement two-way binding to the <b>rangeEnd</b> property.
|
|
656
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
657
|
+
* You can bind handlers to this event in templates using the <b>rangeEndChange</b> event name.
|
|
658
|
+
*/
|
|
659
|
+
rangeEndChangePC: EventEmitter<any>;
|
|
660
|
+
/**
|
|
661
|
+
* Angular (EventEmitter) version of the Wijmo <b>rangeChanged</b> event for programmatic access.
|
|
662
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
663
|
+
* In template bindings use the conventional <b>rangeChanged</b> Wijmo event name.
|
|
664
|
+
*/
|
|
665
|
+
rangeChangedNg: EventEmitter<any>;
|
|
666
|
+
/**
|
|
667
|
+
* Angular (EventEmitter) version of the Wijmo <b>displayMonthChanged</b> event for programmatic access.
|
|
668
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
669
|
+
* In template bindings use the conventional <b>displayMonthChanged</b> Wijmo event name.
|
|
670
|
+
*/
|
|
671
|
+
displayMonthChangedNg: EventEmitter<any>;
|
|
672
|
+
/**
|
|
673
|
+
* This event is used to implement two-way binding to the <b>displayMonth</b> property.
|
|
674
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
675
|
+
* You can bind handlers to this event in templates using the <b>displayMonthChange</b> event name.
|
|
676
|
+
*/
|
|
677
|
+
displayMonthChangePC: EventEmitter<any>;
|
|
678
|
+
/**
|
|
679
|
+
* Angular (EventEmitter) version of the Wijmo <b>formatItem</b> event for programmatic access.
|
|
680
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
681
|
+
* In template bindings use the conventional <b>formatItem</b> Wijmo event name.
|
|
682
|
+
*/
|
|
683
|
+
formatItemNg: EventEmitter<any>;
|
|
684
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
685
|
+
/**
|
|
686
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
687
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
688
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
689
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
690
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
691
|
+
*/
|
|
692
|
+
created(): void;
|
|
693
|
+
ngOnInit(): void;
|
|
694
|
+
ngAfterViewInit(): void;
|
|
695
|
+
ngOnDestroy(): void;
|
|
696
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
697
|
+
}
|
|
698
|
+
declare var wjColorPickerMeta: IWjComponentMeta;
|
|
699
|
+
export { wjColorPickerMeta };
|
|
700
|
+
/**
|
|
701
|
+
* Angular 2 component for the {@link wijmo.input.ColorPicker} control.
|
|
702
|
+
*
|
|
703
|
+
* Use the <b>wj-color-picker</b> component to add <b>ColorPicker</b> controls to your
|
|
704
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
705
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
706
|
+
*
|
|
707
|
+
* The <b>WjColorPicker</b> component is derived from the <b>ColorPicker</b> control and
|
|
708
|
+
* inherits all its properties, events and methods.
|
|
709
|
+
*/
|
|
710
|
+
export declare class WjColorPicker extends wjcInput.ColorPicker implements OnInit, OnDestroy, AfterViewInit {
|
|
711
|
+
static readonly meta: IWjComponentMetadata;
|
|
712
|
+
private _wjBehaviour;
|
|
713
|
+
/**
|
|
714
|
+
* Indicates whether the component has been initialized by Angular.
|
|
715
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
716
|
+
*/
|
|
717
|
+
isInitialized: boolean;
|
|
718
|
+
/**
|
|
719
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
720
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
721
|
+
*/
|
|
722
|
+
initialized: EventEmitter<any>;
|
|
723
|
+
/**
|
|
724
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
725
|
+
* Default value is 'value'.
|
|
726
|
+
*/
|
|
727
|
+
wjModelProperty: string;
|
|
728
|
+
/**
|
|
729
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
730
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
731
|
+
*/
|
|
732
|
+
asyncBindings: boolean;
|
|
733
|
+
/**
|
|
734
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
735
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
736
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
737
|
+
*/
|
|
738
|
+
gotFocusNg: EventEmitter<any>;
|
|
739
|
+
/**
|
|
740
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
741
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
742
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
743
|
+
*/
|
|
744
|
+
lostFocusNg: EventEmitter<any>;
|
|
745
|
+
/**
|
|
746
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
747
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
748
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
749
|
+
*/
|
|
750
|
+
refreshingNg: EventEmitter<any>;
|
|
751
|
+
/**
|
|
752
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
753
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
754
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
755
|
+
*/
|
|
756
|
+
refreshedNg: EventEmitter<any>;
|
|
757
|
+
/**
|
|
758
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
759
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
760
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
761
|
+
*/
|
|
762
|
+
invalidInputNg: EventEmitter<any>;
|
|
763
|
+
/**
|
|
764
|
+
* Angular (EventEmitter) version of the Wijmo <b>valueChanged</b> event for programmatic access.
|
|
765
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
766
|
+
* In template bindings use the conventional <b>valueChanged</b> Wijmo event name.
|
|
767
|
+
*/
|
|
768
|
+
valueChangedNg: EventEmitter<any>;
|
|
769
|
+
/**
|
|
770
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
771
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
772
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
773
|
+
*/
|
|
774
|
+
valueChangePC: EventEmitter<any>;
|
|
775
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
776
|
+
/**
|
|
777
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
778
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
779
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
780
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
781
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
782
|
+
*/
|
|
783
|
+
created(): void;
|
|
784
|
+
ngOnInit(): void;
|
|
785
|
+
ngAfterViewInit(): void;
|
|
786
|
+
ngOnDestroy(): void;
|
|
787
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
788
|
+
}
|
|
789
|
+
declare var wjInputMaskMeta: IWjComponentMeta;
|
|
790
|
+
export { wjInputMaskMeta };
|
|
791
|
+
/**
|
|
792
|
+
* Angular 2 component for the {@link wijmo.input.InputMask} control.
|
|
793
|
+
*
|
|
794
|
+
* Use the <b>wj-input-mask</b> component to add <b>InputMask</b> controls to your
|
|
795
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
796
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
797
|
+
*
|
|
798
|
+
* The <b>WjInputMask</b> component is derived from the <b>InputMask</b> control and
|
|
799
|
+
* inherits all its properties, events and methods.
|
|
800
|
+
*/
|
|
801
|
+
export declare class WjInputMask extends wjcInput.InputMask implements OnInit, OnDestroy, AfterViewInit {
|
|
802
|
+
static readonly meta: IWjComponentMetadata;
|
|
803
|
+
private _wjBehaviour;
|
|
804
|
+
/**
|
|
805
|
+
* Indicates whether the component has been initialized by Angular.
|
|
806
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
807
|
+
*/
|
|
808
|
+
isInitialized: boolean;
|
|
809
|
+
/**
|
|
810
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
811
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
812
|
+
*/
|
|
813
|
+
initialized: EventEmitter<any>;
|
|
814
|
+
/**
|
|
815
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
816
|
+
* Default value is 'value'.
|
|
817
|
+
*/
|
|
818
|
+
wjModelProperty: string;
|
|
819
|
+
/**
|
|
820
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
821
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
822
|
+
*/
|
|
823
|
+
asyncBindings: boolean;
|
|
824
|
+
/**
|
|
825
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
826
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
827
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
828
|
+
*/
|
|
829
|
+
gotFocusNg: EventEmitter<any>;
|
|
830
|
+
/**
|
|
831
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
832
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
833
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
834
|
+
*/
|
|
835
|
+
lostFocusNg: EventEmitter<any>;
|
|
836
|
+
/**
|
|
837
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
838
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
839
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
840
|
+
*/
|
|
841
|
+
refreshingNg: EventEmitter<any>;
|
|
842
|
+
/**
|
|
843
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
844
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
845
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
846
|
+
*/
|
|
847
|
+
refreshedNg: EventEmitter<any>;
|
|
848
|
+
/**
|
|
849
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
850
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
851
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
852
|
+
*/
|
|
853
|
+
invalidInputNg: EventEmitter<any>;
|
|
854
|
+
/**
|
|
855
|
+
* Angular (EventEmitter) version of the Wijmo <b>valueChanged</b> event for programmatic access.
|
|
856
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
857
|
+
* In template bindings use the conventional <b>valueChanged</b> Wijmo event name.
|
|
858
|
+
*/
|
|
859
|
+
valueChangedNg: EventEmitter<any>;
|
|
860
|
+
/**
|
|
861
|
+
* This event is used to implement two-way binding to the <b>rawValue</b> property.
|
|
862
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
863
|
+
* You can bind handlers to this event in templates using the <b>rawValueChange</b> event name.
|
|
864
|
+
*/
|
|
865
|
+
rawValueChangePC: EventEmitter<any>;
|
|
866
|
+
/**
|
|
867
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
868
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
869
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
870
|
+
*/
|
|
871
|
+
valueChangePC: EventEmitter<any>;
|
|
872
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
873
|
+
/**
|
|
874
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
875
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
876
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
877
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
878
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
879
|
+
*/
|
|
880
|
+
created(): void;
|
|
881
|
+
ngOnInit(): void;
|
|
882
|
+
ngAfterViewInit(): void;
|
|
883
|
+
ngOnDestroy(): void;
|
|
884
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
885
|
+
}
|
|
886
|
+
declare var wjInputColorMeta: IWjComponentMeta;
|
|
887
|
+
export { wjInputColorMeta };
|
|
888
|
+
/**
|
|
889
|
+
* Angular 2 component for the {@link wijmo.input.InputColor} control.
|
|
890
|
+
*
|
|
891
|
+
* Use the <b>wj-input-color</b> component to add <b>InputColor</b> controls to your
|
|
892
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
893
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
894
|
+
*
|
|
895
|
+
* The <b>WjInputColor</b> component is derived from the <b>InputColor</b> control and
|
|
896
|
+
* inherits all its properties, events and methods.
|
|
897
|
+
*/
|
|
898
|
+
export declare class WjInputColor extends wjcInput.InputColor implements OnInit, OnDestroy, AfterViewInit {
|
|
899
|
+
static readonly meta: IWjComponentMetadata;
|
|
900
|
+
private _wjBehaviour;
|
|
901
|
+
/**
|
|
902
|
+
* Indicates whether the component has been initialized by Angular.
|
|
903
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
904
|
+
*/
|
|
905
|
+
isInitialized: boolean;
|
|
906
|
+
/**
|
|
907
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
908
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
909
|
+
*/
|
|
910
|
+
initialized: EventEmitter<any>;
|
|
911
|
+
/**
|
|
912
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
913
|
+
* Default value is 'value'.
|
|
914
|
+
*/
|
|
915
|
+
wjModelProperty: string;
|
|
916
|
+
/**
|
|
917
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
918
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
919
|
+
*/
|
|
920
|
+
asyncBindings: boolean;
|
|
921
|
+
/**
|
|
922
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
923
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
924
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
925
|
+
*/
|
|
926
|
+
gotFocusNg: EventEmitter<any>;
|
|
927
|
+
/**
|
|
928
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
929
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
930
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
931
|
+
*/
|
|
932
|
+
lostFocusNg: EventEmitter<any>;
|
|
933
|
+
/**
|
|
934
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
935
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
936
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
937
|
+
*/
|
|
938
|
+
refreshingNg: EventEmitter<any>;
|
|
939
|
+
/**
|
|
940
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
941
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
942
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
943
|
+
*/
|
|
944
|
+
refreshedNg: EventEmitter<any>;
|
|
945
|
+
/**
|
|
946
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
947
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
948
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
949
|
+
*/
|
|
950
|
+
invalidInputNg: EventEmitter<any>;
|
|
951
|
+
/**
|
|
952
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
953
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
954
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
955
|
+
*/
|
|
956
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
957
|
+
/**
|
|
958
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
959
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
960
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
961
|
+
*/
|
|
962
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
963
|
+
/**
|
|
964
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
965
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
966
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
967
|
+
*/
|
|
968
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
969
|
+
/**
|
|
970
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
971
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
972
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
973
|
+
*/
|
|
974
|
+
textChangedNg: EventEmitter<any>;
|
|
975
|
+
/**
|
|
976
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
977
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
978
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
979
|
+
*/
|
|
980
|
+
textChangePC: EventEmitter<any>;
|
|
981
|
+
/**
|
|
982
|
+
* Angular (EventEmitter) version of the Wijmo <b>valueChanged</b> event for programmatic access.
|
|
983
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
984
|
+
* In template bindings use the conventional <b>valueChanged</b> Wijmo event name.
|
|
985
|
+
*/
|
|
986
|
+
valueChangedNg: EventEmitter<any>;
|
|
987
|
+
/**
|
|
988
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
989
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
990
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
991
|
+
*/
|
|
992
|
+
valueChangePC: EventEmitter<any>;
|
|
993
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
994
|
+
/**
|
|
995
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
996
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
997
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
998
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
999
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
1000
|
+
*/
|
|
1001
|
+
created(): void;
|
|
1002
|
+
ngOnInit(): void;
|
|
1003
|
+
ngAfterViewInit(): void;
|
|
1004
|
+
ngOnDestroy(): void;
|
|
1005
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
1006
|
+
}
|
|
1007
|
+
declare var wjMultiSelectMeta: IWjComponentMeta;
|
|
1008
|
+
export { wjMultiSelectMeta };
|
|
1009
|
+
/**
|
|
1010
|
+
* Angular 2 component for the {@link wijmo.input.MultiSelect} control.
|
|
1011
|
+
*
|
|
1012
|
+
* Use the <b>wj-multi-select</b> component to add <b>MultiSelect</b> controls to your
|
|
1013
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
1014
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
1015
|
+
*
|
|
1016
|
+
* The <b>WjMultiSelect</b> component is derived from the <b>MultiSelect</b> control and
|
|
1017
|
+
* inherits all its properties, events and methods.
|
|
1018
|
+
*
|
|
1019
|
+
* The <b>wj-multi-select</b> component may contain a {@link wijmo.angular2legacy.input.WjItemTemplate} child directive.
|
|
1020
|
+
*/
|
|
1021
|
+
export declare class WjMultiSelect extends wjcInput.MultiSelect implements OnInit, OnDestroy, AfterViewInit {
|
|
1022
|
+
static readonly meta: IWjComponentMetadata;
|
|
1023
|
+
private _wjBehaviour;
|
|
1024
|
+
/**
|
|
1025
|
+
* Indicates whether the component has been initialized by Angular.
|
|
1026
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
1027
|
+
*/
|
|
1028
|
+
isInitialized: boolean;
|
|
1029
|
+
/**
|
|
1030
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
1031
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
1032
|
+
*/
|
|
1033
|
+
initialized: EventEmitter<any>;
|
|
1034
|
+
/**
|
|
1035
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
1036
|
+
* Default value is 'checkedItems'.
|
|
1037
|
+
*/
|
|
1038
|
+
wjModelProperty: string;
|
|
1039
|
+
/**
|
|
1040
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
1041
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
1042
|
+
*/
|
|
1043
|
+
asyncBindings: boolean;
|
|
1044
|
+
/**
|
|
1045
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
1046
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1047
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
1048
|
+
*/
|
|
1049
|
+
gotFocusNg: EventEmitter<any>;
|
|
1050
|
+
/**
|
|
1051
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
1052
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1053
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
1054
|
+
*/
|
|
1055
|
+
lostFocusNg: EventEmitter<any>;
|
|
1056
|
+
/**
|
|
1057
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
1058
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1059
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
1060
|
+
*/
|
|
1061
|
+
refreshingNg: EventEmitter<any>;
|
|
1062
|
+
/**
|
|
1063
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
1064
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1065
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
1066
|
+
*/
|
|
1067
|
+
refreshedNg: EventEmitter<any>;
|
|
1068
|
+
/**
|
|
1069
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
1070
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1071
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
1072
|
+
*/
|
|
1073
|
+
invalidInputNg: EventEmitter<any>;
|
|
1074
|
+
/**
|
|
1075
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
1076
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1077
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
1078
|
+
*/
|
|
1079
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
1080
|
+
/**
|
|
1081
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
1082
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1083
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
1084
|
+
*/
|
|
1085
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
1086
|
+
/**
|
|
1087
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
1088
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1089
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
1090
|
+
*/
|
|
1091
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
1092
|
+
/**
|
|
1093
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
1094
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1095
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
1096
|
+
*/
|
|
1097
|
+
textChangedNg: EventEmitter<any>;
|
|
1098
|
+
/**
|
|
1099
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
1100
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1101
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
1102
|
+
*/
|
|
1103
|
+
textChangePC: EventEmitter<any>;
|
|
1104
|
+
/**
|
|
1105
|
+
* Angular (EventEmitter) version of the Wijmo <b>itemsSourceChanged</b> event for programmatic access.
|
|
1106
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1107
|
+
* In template bindings use the conventional <b>itemsSourceChanged</b> Wijmo event name.
|
|
1108
|
+
*/
|
|
1109
|
+
itemsSourceChangedNg: EventEmitter<any>;
|
|
1110
|
+
/**
|
|
1111
|
+
* Angular (EventEmitter) version of the Wijmo <b>formatItem</b> event for programmatic access.
|
|
1112
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1113
|
+
* In template bindings use the conventional <b>formatItem</b> Wijmo event name.
|
|
1114
|
+
*/
|
|
1115
|
+
formatItemNg: EventEmitter<any>;
|
|
1116
|
+
/**
|
|
1117
|
+
* Angular (EventEmitter) version of the Wijmo <b>selectedIndexChanged</b> event for programmatic access.
|
|
1118
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1119
|
+
* In template bindings use the conventional <b>selectedIndexChanged</b> Wijmo event name.
|
|
1120
|
+
*/
|
|
1121
|
+
selectedIndexChangedNg: EventEmitter<any>;
|
|
1122
|
+
/**
|
|
1123
|
+
* This event is used to implement two-way binding to the <b>selectedIndex</b> property.
|
|
1124
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1125
|
+
* You can bind handlers to this event in templates using the <b>selectedIndexChange</b> event name.
|
|
1126
|
+
*/
|
|
1127
|
+
selectedIndexChangePC: EventEmitter<any>;
|
|
1128
|
+
/**
|
|
1129
|
+
* This event is used to implement two-way binding to the <b>selectedItem</b> property.
|
|
1130
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1131
|
+
* You can bind handlers to this event in templates using the <b>selectedItemChange</b> event name.
|
|
1132
|
+
*/
|
|
1133
|
+
selectedItemChangePC: EventEmitter<any>;
|
|
1134
|
+
/**
|
|
1135
|
+
* This event is used to implement two-way binding to the <b>selectedValue</b> property.
|
|
1136
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1137
|
+
* You can bind handlers to this event in templates using the <b>selectedValueChange</b> event name.
|
|
1138
|
+
*/
|
|
1139
|
+
selectedValueChangePC: EventEmitter<any>;
|
|
1140
|
+
/**
|
|
1141
|
+
* Angular (EventEmitter) version of the Wijmo <b>checkedItemsChanged</b> event for programmatic access.
|
|
1142
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1143
|
+
* In template bindings use the conventional <b>checkedItemsChanged</b> Wijmo event name.
|
|
1144
|
+
*/
|
|
1145
|
+
checkedItemsChangedNg: EventEmitter<any>;
|
|
1146
|
+
/**
|
|
1147
|
+
* This event is used to implement two-way binding to the <b>checkedItems</b> property.
|
|
1148
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1149
|
+
* You can bind handlers to this event in templates using the <b>checkedItemsChange</b> event name.
|
|
1150
|
+
*/
|
|
1151
|
+
checkedItemsChangePC: EventEmitter<any>;
|
|
1152
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
1153
|
+
/**
|
|
1154
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
1155
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
1156
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
1157
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
1158
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
1159
|
+
*/
|
|
1160
|
+
created(): void;
|
|
1161
|
+
ngOnInit(): void;
|
|
1162
|
+
ngAfterViewInit(): void;
|
|
1163
|
+
ngOnDestroy(): void;
|
|
1164
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
1165
|
+
}
|
|
1166
|
+
declare var wjMultiAutoCompleteMeta: IWjComponentMeta;
|
|
1167
|
+
export { wjMultiAutoCompleteMeta };
|
|
1168
|
+
/**
|
|
1169
|
+
* Angular 2 component for the {@link wijmo.input.MultiAutoComplete} control.
|
|
1170
|
+
*
|
|
1171
|
+
* Use the <b>wj-multi-auto-complete</b> component to add <b>MultiAutoComplete</b> controls to your
|
|
1172
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
1173
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
1174
|
+
*
|
|
1175
|
+
* The <b>WjMultiAutoComplete</b> component is derived from the <b>MultiAutoComplete</b> control and
|
|
1176
|
+
* inherits all its properties, events and methods.
|
|
1177
|
+
*/
|
|
1178
|
+
export declare class WjMultiAutoComplete extends wjcInput.MultiAutoComplete implements OnInit, OnDestroy, AfterViewInit {
|
|
1179
|
+
static readonly meta: IWjComponentMetadata;
|
|
1180
|
+
private _wjBehaviour;
|
|
1181
|
+
/**
|
|
1182
|
+
* Indicates whether the component has been initialized by Angular.
|
|
1183
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
1184
|
+
*/
|
|
1185
|
+
isInitialized: boolean;
|
|
1186
|
+
/**
|
|
1187
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
1188
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
1189
|
+
*/
|
|
1190
|
+
initialized: EventEmitter<any>;
|
|
1191
|
+
/**
|
|
1192
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
1193
|
+
* Default value is 'selectedItems'.
|
|
1194
|
+
*/
|
|
1195
|
+
wjModelProperty: string;
|
|
1196
|
+
/**
|
|
1197
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
1198
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
1199
|
+
*/
|
|
1200
|
+
asyncBindings: boolean;
|
|
1201
|
+
/**
|
|
1202
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
1203
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1204
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
1205
|
+
*/
|
|
1206
|
+
gotFocusNg: EventEmitter<any>;
|
|
1207
|
+
/**
|
|
1208
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
1209
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1210
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
1211
|
+
*/
|
|
1212
|
+
lostFocusNg: EventEmitter<any>;
|
|
1213
|
+
/**
|
|
1214
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
1215
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1216
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
1217
|
+
*/
|
|
1218
|
+
refreshingNg: EventEmitter<any>;
|
|
1219
|
+
/**
|
|
1220
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
1221
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1222
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
1223
|
+
*/
|
|
1224
|
+
refreshedNg: EventEmitter<any>;
|
|
1225
|
+
/**
|
|
1226
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
1227
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1228
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
1229
|
+
*/
|
|
1230
|
+
invalidInputNg: EventEmitter<any>;
|
|
1231
|
+
/**
|
|
1232
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
1233
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1234
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
1235
|
+
*/
|
|
1236
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
1237
|
+
/**
|
|
1238
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
1239
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1240
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
1241
|
+
*/
|
|
1242
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
1243
|
+
/**
|
|
1244
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
1245
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1246
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
1247
|
+
*/
|
|
1248
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
1249
|
+
/**
|
|
1250
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
1251
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1252
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
1253
|
+
*/
|
|
1254
|
+
textChangedNg: EventEmitter<any>;
|
|
1255
|
+
/**
|
|
1256
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
1257
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1258
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
1259
|
+
*/
|
|
1260
|
+
textChangePC: EventEmitter<any>;
|
|
1261
|
+
/**
|
|
1262
|
+
* Angular (EventEmitter) version of the Wijmo <b>itemsSourceChanged</b> event for programmatic access.
|
|
1263
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1264
|
+
* In template bindings use the conventional <b>itemsSourceChanged</b> Wijmo event name.
|
|
1265
|
+
*/
|
|
1266
|
+
itemsSourceChangedNg: EventEmitter<any>;
|
|
1267
|
+
/**
|
|
1268
|
+
* Angular (EventEmitter) version of the Wijmo <b>formatItem</b> event for programmatic access.
|
|
1269
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1270
|
+
* In template bindings use the conventional <b>formatItem</b> Wijmo event name.
|
|
1271
|
+
*/
|
|
1272
|
+
formatItemNg: EventEmitter<any>;
|
|
1273
|
+
/**
|
|
1274
|
+
* Angular (EventEmitter) version of the Wijmo <b>selectedIndexChanged</b> event for programmatic access.
|
|
1275
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1276
|
+
* In template bindings use the conventional <b>selectedIndexChanged</b> Wijmo event name.
|
|
1277
|
+
*/
|
|
1278
|
+
selectedIndexChangedNg: EventEmitter<any>;
|
|
1279
|
+
/**
|
|
1280
|
+
* This event is used to implement two-way binding to the <b>selectedIndex</b> property.
|
|
1281
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1282
|
+
* You can bind handlers to this event in templates using the <b>selectedIndexChange</b> event name.
|
|
1283
|
+
*/
|
|
1284
|
+
selectedIndexChangePC: EventEmitter<any>;
|
|
1285
|
+
/**
|
|
1286
|
+
* This event is used to implement two-way binding to the <b>selectedItem</b> property.
|
|
1287
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1288
|
+
* You can bind handlers to this event in templates using the <b>selectedItemChange</b> event name.
|
|
1289
|
+
*/
|
|
1290
|
+
selectedItemChangePC: EventEmitter<any>;
|
|
1291
|
+
/**
|
|
1292
|
+
* This event is used to implement two-way binding to the <b>selectedValue</b> property.
|
|
1293
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1294
|
+
* You can bind handlers to this event in templates using the <b>selectedValueChange</b> event name.
|
|
1295
|
+
*/
|
|
1296
|
+
selectedValueChangePC: EventEmitter<any>;
|
|
1297
|
+
/**
|
|
1298
|
+
* Angular (EventEmitter) version of the Wijmo <b>selectedItemsChanged</b> event for programmatic access.
|
|
1299
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1300
|
+
* In template bindings use the conventional <b>selectedItemsChanged</b> Wijmo event name.
|
|
1301
|
+
*/
|
|
1302
|
+
selectedItemsChangedNg: EventEmitter<any>;
|
|
1303
|
+
/**
|
|
1304
|
+
* This event is used to implement two-way binding to the <b>selectedItems</b> property.
|
|
1305
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1306
|
+
* You can bind handlers to this event in templates using the <b>selectedItemsChange</b> event name.
|
|
1307
|
+
*/
|
|
1308
|
+
selectedItemsChangePC: EventEmitter<any>;
|
|
1309
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
1310
|
+
/**
|
|
1311
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
1312
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
1313
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
1314
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
1315
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
1316
|
+
*/
|
|
1317
|
+
created(): void;
|
|
1318
|
+
ngOnInit(): void;
|
|
1319
|
+
ngAfterViewInit(): void;
|
|
1320
|
+
ngOnDestroy(): void;
|
|
1321
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
1322
|
+
}
|
|
1323
|
+
declare var wjInputNumberMeta: IWjComponentMeta;
|
|
1324
|
+
export { wjInputNumberMeta };
|
|
1325
|
+
/**
|
|
1326
|
+
* Angular 2 component for the {@link wijmo.input.InputNumber} control.
|
|
1327
|
+
*
|
|
1328
|
+
* Use the <b>wj-input-number</b> component to add <b>InputNumber</b> controls to your
|
|
1329
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
1330
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
1331
|
+
*
|
|
1332
|
+
* The <b>WjInputNumber</b> component is derived from the <b>InputNumber</b> control and
|
|
1333
|
+
* inherits all its properties, events and methods.
|
|
1334
|
+
*/
|
|
1335
|
+
export declare class WjInputNumber extends wjcInput.InputNumber implements OnInit, OnDestroy, AfterViewInit {
|
|
1336
|
+
static readonly meta: IWjComponentMetadata;
|
|
1337
|
+
private _wjBehaviour;
|
|
1338
|
+
/**
|
|
1339
|
+
* Indicates whether the component has been initialized by Angular.
|
|
1340
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
1341
|
+
*/
|
|
1342
|
+
isInitialized: boolean;
|
|
1343
|
+
/**
|
|
1344
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
1345
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
1346
|
+
*/
|
|
1347
|
+
initialized: EventEmitter<any>;
|
|
1348
|
+
/**
|
|
1349
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
1350
|
+
* Default value is 'value'.
|
|
1351
|
+
*/
|
|
1352
|
+
wjModelProperty: string;
|
|
1353
|
+
/**
|
|
1354
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
1355
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
1356
|
+
*/
|
|
1357
|
+
asyncBindings: boolean;
|
|
1358
|
+
/**
|
|
1359
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
1360
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1361
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
1362
|
+
*/
|
|
1363
|
+
gotFocusNg: EventEmitter<any>;
|
|
1364
|
+
/**
|
|
1365
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
1366
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1367
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
1368
|
+
*/
|
|
1369
|
+
lostFocusNg: EventEmitter<any>;
|
|
1370
|
+
/**
|
|
1371
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
1372
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1373
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
1374
|
+
*/
|
|
1375
|
+
refreshingNg: EventEmitter<any>;
|
|
1376
|
+
/**
|
|
1377
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
1378
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1379
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
1380
|
+
*/
|
|
1381
|
+
refreshedNg: EventEmitter<any>;
|
|
1382
|
+
/**
|
|
1383
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
1384
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1385
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
1386
|
+
*/
|
|
1387
|
+
invalidInputNg: EventEmitter<any>;
|
|
1388
|
+
/**
|
|
1389
|
+
* Angular (EventEmitter) version of the Wijmo <b>valueChanged</b> event for programmatic access.
|
|
1390
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1391
|
+
* In template bindings use the conventional <b>valueChanged</b> Wijmo event name.
|
|
1392
|
+
*/
|
|
1393
|
+
valueChangedNg: EventEmitter<any>;
|
|
1394
|
+
/**
|
|
1395
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
1396
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1397
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
1398
|
+
*/
|
|
1399
|
+
valueChangePC: EventEmitter<any>;
|
|
1400
|
+
/**
|
|
1401
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
1402
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1403
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
1404
|
+
*/
|
|
1405
|
+
textChangedNg: EventEmitter<any>;
|
|
1406
|
+
/**
|
|
1407
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
1408
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1409
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
1410
|
+
*/
|
|
1411
|
+
textChangePC: EventEmitter<any>;
|
|
1412
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
1413
|
+
/**
|
|
1414
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
1415
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
1416
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
1417
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
1418
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
1419
|
+
*/
|
|
1420
|
+
created(): void;
|
|
1421
|
+
ngOnInit(): void;
|
|
1422
|
+
ngAfterViewInit(): void;
|
|
1423
|
+
ngOnDestroy(): void;
|
|
1424
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
1425
|
+
}
|
|
1426
|
+
declare var wjInputDateMeta: IWjComponentMeta;
|
|
1427
|
+
export { wjInputDateMeta };
|
|
1428
|
+
/**
|
|
1429
|
+
* Angular 2 component for the {@link wijmo.input.InputDate} control.
|
|
1430
|
+
*
|
|
1431
|
+
* Use the <b>wj-input-date</b> component to add <b>InputDate</b> controls to your
|
|
1432
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
1433
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
1434
|
+
*
|
|
1435
|
+
* The <b>WjInputDate</b> component is derived from the <b>InputDate</b> control and
|
|
1436
|
+
* inherits all its properties, events and methods.
|
|
1437
|
+
*/
|
|
1438
|
+
export declare class WjInputDate extends wjcInput.InputDate implements OnInit, OnDestroy, AfterViewInit {
|
|
1439
|
+
static readonly meta: IWjComponentMetadata;
|
|
1440
|
+
private _wjBehaviour;
|
|
1441
|
+
/**
|
|
1442
|
+
* Indicates whether the component has been initialized by Angular.
|
|
1443
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
1444
|
+
*/
|
|
1445
|
+
isInitialized: boolean;
|
|
1446
|
+
/**
|
|
1447
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
1448
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
1449
|
+
*/
|
|
1450
|
+
initialized: EventEmitter<any>;
|
|
1451
|
+
/**
|
|
1452
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
1453
|
+
* Default value is 'value'.
|
|
1454
|
+
*/
|
|
1455
|
+
wjModelProperty: string;
|
|
1456
|
+
/**
|
|
1457
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
1458
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
1459
|
+
*/
|
|
1460
|
+
asyncBindings: boolean;
|
|
1461
|
+
/**
|
|
1462
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
1463
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1464
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
1465
|
+
*/
|
|
1466
|
+
gotFocusNg: EventEmitter<any>;
|
|
1467
|
+
/**
|
|
1468
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
1469
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1470
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
1471
|
+
*/
|
|
1472
|
+
lostFocusNg: EventEmitter<any>;
|
|
1473
|
+
/**
|
|
1474
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
1475
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1476
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
1477
|
+
*/
|
|
1478
|
+
refreshingNg: EventEmitter<any>;
|
|
1479
|
+
/**
|
|
1480
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
1481
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1482
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
1483
|
+
*/
|
|
1484
|
+
refreshedNg: EventEmitter<any>;
|
|
1485
|
+
/**
|
|
1486
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
1487
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1488
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
1489
|
+
*/
|
|
1490
|
+
invalidInputNg: EventEmitter<any>;
|
|
1491
|
+
/**
|
|
1492
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
1493
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1494
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
1495
|
+
*/
|
|
1496
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
1497
|
+
/**
|
|
1498
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
1499
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1500
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
1501
|
+
*/
|
|
1502
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
1503
|
+
/**
|
|
1504
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
1505
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1506
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
1507
|
+
*/
|
|
1508
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
1509
|
+
/**
|
|
1510
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
1511
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1512
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
1513
|
+
*/
|
|
1514
|
+
textChangedNg: EventEmitter<any>;
|
|
1515
|
+
/**
|
|
1516
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
1517
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1518
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
1519
|
+
*/
|
|
1520
|
+
textChangePC: EventEmitter<any>;
|
|
1521
|
+
/**
|
|
1522
|
+
* Angular (EventEmitter) version of the Wijmo <b>valueChanged</b> event for programmatic access.
|
|
1523
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1524
|
+
* In template bindings use the conventional <b>valueChanged</b> Wijmo event name.
|
|
1525
|
+
*/
|
|
1526
|
+
valueChangedNg: EventEmitter<any>;
|
|
1527
|
+
/**
|
|
1528
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
1529
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1530
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
1531
|
+
*/
|
|
1532
|
+
valueChangePC: EventEmitter<any>;
|
|
1533
|
+
/**
|
|
1534
|
+
* Angular (EventEmitter) version of the Wijmo <b>rangeEndChanged</b> event for programmatic access.
|
|
1535
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1536
|
+
* In template bindings use the conventional <b>rangeEndChanged</b> Wijmo event name.
|
|
1537
|
+
*/
|
|
1538
|
+
rangeEndChangedNg: EventEmitter<any>;
|
|
1539
|
+
/**
|
|
1540
|
+
* This event is used to implement two-way binding to the <b>rangeEnd</b> property.
|
|
1541
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1542
|
+
* You can bind handlers to this event in templates using the <b>rangeEndChange</b> event name.
|
|
1543
|
+
*/
|
|
1544
|
+
rangeEndChangePC: EventEmitter<any>;
|
|
1545
|
+
/**
|
|
1546
|
+
* Angular (EventEmitter) version of the Wijmo <b>rangeChanged</b> event for programmatic access.
|
|
1547
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1548
|
+
* In template bindings use the conventional <b>rangeChanged</b> Wijmo event name.
|
|
1549
|
+
*/
|
|
1550
|
+
rangeChangedNg: EventEmitter<any>;
|
|
1551
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
1552
|
+
/**
|
|
1553
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
1554
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
1555
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
1556
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
1557
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
1558
|
+
*/
|
|
1559
|
+
created(): void;
|
|
1560
|
+
ngOnInit(): void;
|
|
1561
|
+
ngAfterViewInit(): void;
|
|
1562
|
+
ngOnDestroy(): void;
|
|
1563
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
1564
|
+
}
|
|
1565
|
+
declare var wjInputTimeMeta: IWjComponentMeta;
|
|
1566
|
+
export { wjInputTimeMeta };
|
|
1567
|
+
/**
|
|
1568
|
+
* Angular 2 component for the {@link wijmo.input.InputTime} control.
|
|
1569
|
+
*
|
|
1570
|
+
* Use the <b>wj-input-time</b> component to add <b>InputTime</b> controls to your
|
|
1571
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
1572
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
1573
|
+
*
|
|
1574
|
+
* The <b>WjInputTime</b> component is derived from the <b>InputTime</b> control and
|
|
1575
|
+
* inherits all its properties, events and methods.
|
|
1576
|
+
*/
|
|
1577
|
+
export declare class WjInputTime extends wjcInput.InputTime implements OnInit, OnDestroy, AfterViewInit {
|
|
1578
|
+
static readonly meta: IWjComponentMetadata;
|
|
1579
|
+
private _wjBehaviour;
|
|
1580
|
+
/**
|
|
1581
|
+
* Indicates whether the component has been initialized by Angular.
|
|
1582
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
1583
|
+
*/
|
|
1584
|
+
isInitialized: boolean;
|
|
1585
|
+
/**
|
|
1586
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
1587
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
1588
|
+
*/
|
|
1589
|
+
initialized: EventEmitter<any>;
|
|
1590
|
+
/**
|
|
1591
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
1592
|
+
* Default value is 'value'.
|
|
1593
|
+
*/
|
|
1594
|
+
wjModelProperty: string;
|
|
1595
|
+
/**
|
|
1596
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
1597
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
1598
|
+
*/
|
|
1599
|
+
asyncBindings: boolean;
|
|
1600
|
+
/**
|
|
1601
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
1602
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1603
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
1604
|
+
*/
|
|
1605
|
+
gotFocusNg: EventEmitter<any>;
|
|
1606
|
+
/**
|
|
1607
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
1608
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1609
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
1610
|
+
*/
|
|
1611
|
+
lostFocusNg: EventEmitter<any>;
|
|
1612
|
+
/**
|
|
1613
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
1614
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1615
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
1616
|
+
*/
|
|
1617
|
+
refreshingNg: EventEmitter<any>;
|
|
1618
|
+
/**
|
|
1619
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
1620
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1621
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
1622
|
+
*/
|
|
1623
|
+
refreshedNg: EventEmitter<any>;
|
|
1624
|
+
/**
|
|
1625
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
1626
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1627
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
1628
|
+
*/
|
|
1629
|
+
invalidInputNg: EventEmitter<any>;
|
|
1630
|
+
/**
|
|
1631
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
1632
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1633
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
1634
|
+
*/
|
|
1635
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
1636
|
+
/**
|
|
1637
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
1638
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1639
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
1640
|
+
*/
|
|
1641
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
1642
|
+
/**
|
|
1643
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
1644
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1645
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
1646
|
+
*/
|
|
1647
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
1648
|
+
/**
|
|
1649
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
1650
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1651
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
1652
|
+
*/
|
|
1653
|
+
textChangedNg: EventEmitter<any>;
|
|
1654
|
+
/**
|
|
1655
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
1656
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1657
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
1658
|
+
*/
|
|
1659
|
+
textChangePC: EventEmitter<any>;
|
|
1660
|
+
/**
|
|
1661
|
+
* Angular (EventEmitter) version of the Wijmo <b>itemsSourceChanged</b> event for programmatic access.
|
|
1662
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1663
|
+
* In template bindings use the conventional <b>itemsSourceChanged</b> Wijmo event name.
|
|
1664
|
+
*/
|
|
1665
|
+
itemsSourceChangedNg: EventEmitter<any>;
|
|
1666
|
+
/**
|
|
1667
|
+
* Angular (EventEmitter) version of the Wijmo <b>formatItem</b> event for programmatic access.
|
|
1668
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1669
|
+
* In template bindings use the conventional <b>formatItem</b> Wijmo event name.
|
|
1670
|
+
*/
|
|
1671
|
+
formatItemNg: EventEmitter<any>;
|
|
1672
|
+
/**
|
|
1673
|
+
* Angular (EventEmitter) version of the Wijmo <b>selectedIndexChanged</b> event for programmatic access.
|
|
1674
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1675
|
+
* In template bindings use the conventional <b>selectedIndexChanged</b> Wijmo event name.
|
|
1676
|
+
*/
|
|
1677
|
+
selectedIndexChangedNg: EventEmitter<any>;
|
|
1678
|
+
/**
|
|
1679
|
+
* This event is used to implement two-way binding to the <b>selectedIndex</b> property.
|
|
1680
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1681
|
+
* You can bind handlers to this event in templates using the <b>selectedIndexChange</b> event name.
|
|
1682
|
+
*/
|
|
1683
|
+
selectedIndexChangePC: EventEmitter<any>;
|
|
1684
|
+
/**
|
|
1685
|
+
* This event is used to implement two-way binding to the <b>selectedItem</b> property.
|
|
1686
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1687
|
+
* You can bind handlers to this event in templates using the <b>selectedItemChange</b> event name.
|
|
1688
|
+
*/
|
|
1689
|
+
selectedItemChangePC: EventEmitter<any>;
|
|
1690
|
+
/**
|
|
1691
|
+
* This event is used to implement two-way binding to the <b>selectedValue</b> property.
|
|
1692
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1693
|
+
* You can bind handlers to this event in templates using the <b>selectedValueChange</b> event name.
|
|
1694
|
+
*/
|
|
1695
|
+
selectedValueChangePC: EventEmitter<any>;
|
|
1696
|
+
/**
|
|
1697
|
+
* Angular (EventEmitter) version of the Wijmo <b>valueChanged</b> event for programmatic access.
|
|
1698
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1699
|
+
* In template bindings use the conventional <b>valueChanged</b> Wijmo event name.
|
|
1700
|
+
*/
|
|
1701
|
+
valueChangedNg: EventEmitter<any>;
|
|
1702
|
+
/**
|
|
1703
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
1704
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1705
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
1706
|
+
*/
|
|
1707
|
+
valueChangePC: EventEmitter<any>;
|
|
1708
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
1709
|
+
/**
|
|
1710
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
1711
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
1712
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
1713
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
1714
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
1715
|
+
*/
|
|
1716
|
+
created(): void;
|
|
1717
|
+
ngOnInit(): void;
|
|
1718
|
+
ngAfterViewInit(): void;
|
|
1719
|
+
ngOnDestroy(): void;
|
|
1720
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
1721
|
+
}
|
|
1722
|
+
declare var wjInputDateTimeMeta: IWjComponentMeta;
|
|
1723
|
+
export { wjInputDateTimeMeta };
|
|
1724
|
+
/**
|
|
1725
|
+
* Angular 2 component for the {@link wijmo.input.InputDateTime} control.
|
|
1726
|
+
*
|
|
1727
|
+
* Use the <b>wj-input-date-time</b> component to add <b>InputDateTime</b> controls to your
|
|
1728
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
1729
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
1730
|
+
*
|
|
1731
|
+
* The <b>WjInputDateTime</b> component is derived from the <b>InputDateTime</b> control and
|
|
1732
|
+
* inherits all its properties, events and methods.
|
|
1733
|
+
*/
|
|
1734
|
+
export declare class WjInputDateTime extends wjcInput.InputDateTime implements OnInit, OnDestroy, AfterViewInit {
|
|
1735
|
+
static readonly meta: IWjComponentMetadata;
|
|
1736
|
+
private _wjBehaviour;
|
|
1737
|
+
/**
|
|
1738
|
+
* Indicates whether the component has been initialized by Angular.
|
|
1739
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
1740
|
+
*/
|
|
1741
|
+
isInitialized: boolean;
|
|
1742
|
+
/**
|
|
1743
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
1744
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
1745
|
+
*/
|
|
1746
|
+
initialized: EventEmitter<any>;
|
|
1747
|
+
/**
|
|
1748
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
1749
|
+
* Default value is 'value'.
|
|
1750
|
+
*/
|
|
1751
|
+
wjModelProperty: string;
|
|
1752
|
+
/**
|
|
1753
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
1754
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
1755
|
+
*/
|
|
1756
|
+
asyncBindings: boolean;
|
|
1757
|
+
/**
|
|
1758
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
1759
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1760
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
1761
|
+
*/
|
|
1762
|
+
gotFocusNg: EventEmitter<any>;
|
|
1763
|
+
/**
|
|
1764
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
1765
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1766
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
1767
|
+
*/
|
|
1768
|
+
lostFocusNg: EventEmitter<any>;
|
|
1769
|
+
/**
|
|
1770
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
1771
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1772
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
1773
|
+
*/
|
|
1774
|
+
refreshingNg: EventEmitter<any>;
|
|
1775
|
+
/**
|
|
1776
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
1777
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1778
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
1779
|
+
*/
|
|
1780
|
+
refreshedNg: EventEmitter<any>;
|
|
1781
|
+
/**
|
|
1782
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
1783
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1784
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
1785
|
+
*/
|
|
1786
|
+
invalidInputNg: EventEmitter<any>;
|
|
1787
|
+
/**
|
|
1788
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
1789
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1790
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
1791
|
+
*/
|
|
1792
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
1793
|
+
/**
|
|
1794
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
1795
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1796
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
1797
|
+
*/
|
|
1798
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
1799
|
+
/**
|
|
1800
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
1801
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1802
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
1803
|
+
*/
|
|
1804
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
1805
|
+
/**
|
|
1806
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
1807
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1808
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
1809
|
+
*/
|
|
1810
|
+
textChangedNg: EventEmitter<any>;
|
|
1811
|
+
/**
|
|
1812
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
1813
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1814
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
1815
|
+
*/
|
|
1816
|
+
textChangePC: EventEmitter<any>;
|
|
1817
|
+
/**
|
|
1818
|
+
* Angular (EventEmitter) version of the Wijmo <b>valueChanged</b> event for programmatic access.
|
|
1819
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1820
|
+
* In template bindings use the conventional <b>valueChanged</b> Wijmo event name.
|
|
1821
|
+
*/
|
|
1822
|
+
valueChangedNg: EventEmitter<any>;
|
|
1823
|
+
/**
|
|
1824
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
1825
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1826
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
1827
|
+
*/
|
|
1828
|
+
valueChangePC: EventEmitter<any>;
|
|
1829
|
+
/**
|
|
1830
|
+
* Angular (EventEmitter) version of the Wijmo <b>rangeEndChanged</b> event for programmatic access.
|
|
1831
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1832
|
+
* In template bindings use the conventional <b>rangeEndChanged</b> Wijmo event name.
|
|
1833
|
+
*/
|
|
1834
|
+
rangeEndChangedNg: EventEmitter<any>;
|
|
1835
|
+
/**
|
|
1836
|
+
* This event is used to implement two-way binding to the <b>rangeEnd</b> property.
|
|
1837
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1838
|
+
* You can bind handlers to this event in templates using the <b>rangeEndChange</b> event name.
|
|
1839
|
+
*/
|
|
1840
|
+
rangeEndChangePC: EventEmitter<any>;
|
|
1841
|
+
/**
|
|
1842
|
+
* Angular (EventEmitter) version of the Wijmo <b>rangeChanged</b> event for programmatic access.
|
|
1843
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1844
|
+
* In template bindings use the conventional <b>rangeChanged</b> Wijmo event name.
|
|
1845
|
+
*/
|
|
1846
|
+
rangeChangedNg: EventEmitter<any>;
|
|
1847
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
1848
|
+
/**
|
|
1849
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
1850
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
1851
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
1852
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
1853
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
1854
|
+
*/
|
|
1855
|
+
created(): void;
|
|
1856
|
+
ngOnInit(): void;
|
|
1857
|
+
ngAfterViewInit(): void;
|
|
1858
|
+
ngOnDestroy(): void;
|
|
1859
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
1860
|
+
}
|
|
1861
|
+
declare var wjInputDateRangeMeta: IWjComponentMeta;
|
|
1862
|
+
export { wjInputDateRangeMeta };
|
|
1863
|
+
/**
|
|
1864
|
+
* Angular 2 component for the {@link wijmo.input.InputDateRange} control.
|
|
1865
|
+
*
|
|
1866
|
+
* Use the <b>wj-input-date-range</b> component to add <b>InputDateRange</b> controls to your
|
|
1867
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
1868
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
1869
|
+
*
|
|
1870
|
+
* The <b>WjInputDateRange</b> component is derived from the <b>InputDateRange</b> control and
|
|
1871
|
+
* inherits all its properties, events and methods.
|
|
1872
|
+
*/
|
|
1873
|
+
export declare class WjInputDateRange extends wjcInput.InputDateRange implements OnInit, OnDestroy, AfterViewInit {
|
|
1874
|
+
static readonly meta: IWjComponentMetadata;
|
|
1875
|
+
private _wjBehaviour;
|
|
1876
|
+
/**
|
|
1877
|
+
* Indicates whether the component has been initialized by Angular.
|
|
1878
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
1879
|
+
*/
|
|
1880
|
+
isInitialized: boolean;
|
|
1881
|
+
/**
|
|
1882
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
1883
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
1884
|
+
*/
|
|
1885
|
+
initialized: EventEmitter<any>;
|
|
1886
|
+
/**
|
|
1887
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
1888
|
+
* Default value is 'value'.
|
|
1889
|
+
*/
|
|
1890
|
+
wjModelProperty: string;
|
|
1891
|
+
/**
|
|
1892
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
1893
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
1894
|
+
*/
|
|
1895
|
+
asyncBindings: boolean;
|
|
1896
|
+
/**
|
|
1897
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
1898
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1899
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
1900
|
+
*/
|
|
1901
|
+
gotFocusNg: EventEmitter<any>;
|
|
1902
|
+
/**
|
|
1903
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
1904
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1905
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
1906
|
+
*/
|
|
1907
|
+
lostFocusNg: EventEmitter<any>;
|
|
1908
|
+
/**
|
|
1909
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
1910
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1911
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
1912
|
+
*/
|
|
1913
|
+
refreshingNg: EventEmitter<any>;
|
|
1914
|
+
/**
|
|
1915
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
1916
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1917
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
1918
|
+
*/
|
|
1919
|
+
refreshedNg: EventEmitter<any>;
|
|
1920
|
+
/**
|
|
1921
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
1922
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1923
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
1924
|
+
*/
|
|
1925
|
+
invalidInputNg: EventEmitter<any>;
|
|
1926
|
+
/**
|
|
1927
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
1928
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1929
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
1930
|
+
*/
|
|
1931
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
1932
|
+
/**
|
|
1933
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
1934
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1935
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
1936
|
+
*/
|
|
1937
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
1938
|
+
/**
|
|
1939
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
1940
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1941
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
1942
|
+
*/
|
|
1943
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
1944
|
+
/**
|
|
1945
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
1946
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1947
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
1948
|
+
*/
|
|
1949
|
+
textChangedNg: EventEmitter<any>;
|
|
1950
|
+
/**
|
|
1951
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
1952
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1953
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
1954
|
+
*/
|
|
1955
|
+
textChangePC: EventEmitter<any>;
|
|
1956
|
+
/**
|
|
1957
|
+
* Angular (EventEmitter) version of the Wijmo <b>valueChanged</b> event for programmatic access.
|
|
1958
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1959
|
+
* In template bindings use the conventional <b>valueChanged</b> Wijmo event name.
|
|
1960
|
+
*/
|
|
1961
|
+
valueChangedNg: EventEmitter<any>;
|
|
1962
|
+
/**
|
|
1963
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
1964
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1965
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
1966
|
+
*/
|
|
1967
|
+
valueChangePC: EventEmitter<any>;
|
|
1968
|
+
/**
|
|
1969
|
+
* Angular (EventEmitter) version of the Wijmo <b>rangeEndChanged</b> event for programmatic access.
|
|
1970
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1971
|
+
* In template bindings use the conventional <b>rangeEndChanged</b> Wijmo event name.
|
|
1972
|
+
*/
|
|
1973
|
+
rangeEndChangedNg: EventEmitter<any>;
|
|
1974
|
+
/**
|
|
1975
|
+
* This event is used to implement two-way binding to the <b>rangeEnd</b> property.
|
|
1976
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
1977
|
+
* You can bind handlers to this event in templates using the <b>rangeEndChange</b> event name.
|
|
1978
|
+
*/
|
|
1979
|
+
rangeEndChangePC: EventEmitter<any>;
|
|
1980
|
+
/**
|
|
1981
|
+
* Angular (EventEmitter) version of the Wijmo <b>rangeChanged</b> event for programmatic access.
|
|
1982
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
1983
|
+
* In template bindings use the conventional <b>rangeChanged</b> Wijmo event name.
|
|
1984
|
+
*/
|
|
1985
|
+
rangeChangedNg: EventEmitter<any>;
|
|
1986
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
1987
|
+
/**
|
|
1988
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
1989
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
1990
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
1991
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
1992
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
1993
|
+
*/
|
|
1994
|
+
created(): void;
|
|
1995
|
+
ngOnInit(): void;
|
|
1996
|
+
ngAfterViewInit(): void;
|
|
1997
|
+
ngOnDestroy(): void;
|
|
1998
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
1999
|
+
}
|
|
2000
|
+
declare var wjMenuMeta: IWjComponentMeta;
|
|
2001
|
+
export { wjMenuMeta };
|
|
2002
|
+
/**
|
|
2003
|
+
* Angular 2 component for the {@link wijmo.input.Menu} control.
|
|
2004
|
+
*
|
|
2005
|
+
* Use the <b>wj-menu</b> component to add <b>Menu</b> controls to your
|
|
2006
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
2007
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
2008
|
+
*
|
|
2009
|
+
* The <b>WjMenu</b> component is derived from the <b>Menu</b> control and
|
|
2010
|
+
* inherits all its properties, events and methods.
|
|
2011
|
+
*
|
|
2012
|
+
* The <b>wj-menu</b> component may contain the following child components:
|
|
2013
|
+
* {@link wijmo.angular2legacy.input.WjMenuItem}
|
|
2014
|
+
* , {@link wijmo.angular2legacy.input.WjMenuSeparator}
|
|
2015
|
+
* and {@link wijmo.angular2legacy.input.WjItemTemplate}.
|
|
2016
|
+
*/
|
|
2017
|
+
export declare class WjMenu extends wjcInput.Menu implements OnInit, OnDestroy, AfterViewInit, OnChanges, AfterContentInit {
|
|
2018
|
+
private _value;
|
|
2019
|
+
private _definedHeader;
|
|
2020
|
+
static readonly meta: IWjComponentMetadata;
|
|
2021
|
+
private _wjBehaviour;
|
|
2022
|
+
/**
|
|
2023
|
+
* Indicates whether the component has been initialized by Angular.
|
|
2024
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
2025
|
+
*/
|
|
2026
|
+
isInitialized: boolean;
|
|
2027
|
+
/**
|
|
2028
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
2029
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
2030
|
+
*/
|
|
2031
|
+
initialized: EventEmitter<any>;
|
|
2032
|
+
/**
|
|
2033
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
2034
|
+
* Default value is 'selectedValue'.
|
|
2035
|
+
*/
|
|
2036
|
+
wjModelProperty: string;
|
|
2037
|
+
/**
|
|
2038
|
+
* Allows you to override the global <b>WjOptions.asyncBindings</b> setting for this specific component.
|
|
2039
|
+
* See the <b>WjOptions.</b>{@link WjOptions.asyncBindings} property description for details.
|
|
2040
|
+
*/
|
|
2041
|
+
asyncBindings: boolean;
|
|
2042
|
+
/**
|
|
2043
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
2044
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2045
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
2046
|
+
*/
|
|
2047
|
+
gotFocusNg: EventEmitter<any>;
|
|
2048
|
+
/**
|
|
2049
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
2050
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2051
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
2052
|
+
*/
|
|
2053
|
+
lostFocusNg: EventEmitter<any>;
|
|
2054
|
+
/**
|
|
2055
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
2056
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2057
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
2058
|
+
*/
|
|
2059
|
+
refreshingNg: EventEmitter<any>;
|
|
2060
|
+
/**
|
|
2061
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
2062
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2063
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
2064
|
+
*/
|
|
2065
|
+
refreshedNg: EventEmitter<any>;
|
|
2066
|
+
/**
|
|
2067
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
2068
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2069
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
2070
|
+
*/
|
|
2071
|
+
invalidInputNg: EventEmitter<any>;
|
|
2072
|
+
/**
|
|
2073
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanging</b> event for programmatic access.
|
|
2074
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2075
|
+
* In template bindings use the conventional <b>isDroppedDownChanging</b> Wijmo event name.
|
|
2076
|
+
*/
|
|
2077
|
+
isDroppedDownChangingNg: EventEmitter<any>;
|
|
2078
|
+
/**
|
|
2079
|
+
* Angular (EventEmitter) version of the Wijmo <b>isDroppedDownChanged</b> event for programmatic access.
|
|
2080
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2081
|
+
* In template bindings use the conventional <b>isDroppedDownChanged</b> Wijmo event name.
|
|
2082
|
+
*/
|
|
2083
|
+
isDroppedDownChangedNg: EventEmitter<any>;
|
|
2084
|
+
/**
|
|
2085
|
+
* This event is used to implement two-way binding to the <b>isDroppedDown</b> property.
|
|
2086
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
2087
|
+
* You can bind handlers to this event in templates using the <b>isDroppedDownChange</b> event name.
|
|
2088
|
+
*/
|
|
2089
|
+
isDroppedDownChangePC: EventEmitter<any>;
|
|
2090
|
+
/**
|
|
2091
|
+
* Angular (EventEmitter) version of the Wijmo <b>textChanged</b> event for programmatic access.
|
|
2092
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2093
|
+
* In template bindings use the conventional <b>textChanged</b> Wijmo event name.
|
|
2094
|
+
*/
|
|
2095
|
+
textChangedNg: EventEmitter<any>;
|
|
2096
|
+
/**
|
|
2097
|
+
* This event is used to implement two-way binding to the <b>text</b> property.
|
|
2098
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
2099
|
+
* You can bind handlers to this event in templates using the <b>textChange</b> event name.
|
|
2100
|
+
*/
|
|
2101
|
+
textChangePC: EventEmitter<any>;
|
|
2102
|
+
/**
|
|
2103
|
+
* Angular (EventEmitter) version of the Wijmo <b>itemsSourceChanged</b> event for programmatic access.
|
|
2104
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2105
|
+
* In template bindings use the conventional <b>itemsSourceChanged</b> Wijmo event name.
|
|
2106
|
+
*/
|
|
2107
|
+
itemsSourceChangedNg: EventEmitter<any>;
|
|
2108
|
+
/**
|
|
2109
|
+
* Angular (EventEmitter) version of the Wijmo <b>formatItem</b> event for programmatic access.
|
|
2110
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2111
|
+
* In template bindings use the conventional <b>formatItem</b> Wijmo event name.
|
|
2112
|
+
*/
|
|
2113
|
+
formatItemNg: EventEmitter<any>;
|
|
2114
|
+
/**
|
|
2115
|
+
* Angular (EventEmitter) version of the Wijmo <b>selectedIndexChanged</b> event for programmatic access.
|
|
2116
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2117
|
+
* In template bindings use the conventional <b>selectedIndexChanged</b> Wijmo event name.
|
|
2118
|
+
*/
|
|
2119
|
+
selectedIndexChangedNg: EventEmitter<any>;
|
|
2120
|
+
/**
|
|
2121
|
+
* This event is used to implement two-way binding to the <b>selectedIndex</b> property.
|
|
2122
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
2123
|
+
* You can bind handlers to this event in templates using the <b>selectedIndexChange</b> event name.
|
|
2124
|
+
*/
|
|
2125
|
+
selectedIndexChangePC: EventEmitter<any>;
|
|
2126
|
+
/**
|
|
2127
|
+
* This event is used to implement two-way binding to the <b>selectedItem</b> property.
|
|
2128
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
2129
|
+
* You can bind handlers to this event in templates using the <b>selectedItemChange</b> event name.
|
|
2130
|
+
*/
|
|
2131
|
+
selectedItemChangePC: EventEmitter<any>;
|
|
2132
|
+
/**
|
|
2133
|
+
* This event is used to implement two-way binding to the <b>selectedValue</b> property.
|
|
2134
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
2135
|
+
* You can bind handlers to this event in templates using the <b>selectedValueChange</b> event name.
|
|
2136
|
+
*/
|
|
2137
|
+
selectedValueChangePC: EventEmitter<any>;
|
|
2138
|
+
/**
|
|
2139
|
+
* Angular (EventEmitter) version of the Wijmo <b>itemClicked</b> event for programmatic access.
|
|
2140
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2141
|
+
* In template bindings use the conventional <b>itemClicked</b> Wijmo event name.
|
|
2142
|
+
*/
|
|
2143
|
+
itemClickedNg: EventEmitter<any>;
|
|
2144
|
+
/**
|
|
2145
|
+
* This event is used to implement two-way binding to the <b>value</b> property.
|
|
2146
|
+
* It's triggered when the property value changes, with the event argument holding the new property value.
|
|
2147
|
+
* You can bind handlers to this event in templates using the <b>valueChange</b> event name.
|
|
2148
|
+
*/
|
|
2149
|
+
valueChangePC: EventEmitter<any>;
|
|
2150
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
2151
|
+
/**
|
|
2152
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
2153
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
2154
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
2155
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
2156
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
2157
|
+
*/
|
|
2158
|
+
created(): void;
|
|
2159
|
+
ngOnInit(): void;
|
|
2160
|
+
ngAfterViewInit(): void;
|
|
2161
|
+
ngOnDestroy(): void;
|
|
2162
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
2163
|
+
value: any;
|
|
2164
|
+
ngOnChanges(changes: {
|
|
2165
|
+
[key: string]: ngCore.SimpleChange;
|
|
2166
|
+
}): void;
|
|
2167
|
+
ngAfterContentInit(): void;
|
|
2168
|
+
onItemClicked(e?: wjcCore.EventArgs): void;
|
|
2169
|
+
refresh(fullUpdate?: boolean): void;
|
|
2170
|
+
private _attachToControl;
|
|
2171
|
+
private _loadingItems;
|
|
2172
|
+
private _fmtItem;
|
|
2173
|
+
private _updateHeader;
|
|
2174
|
+
}
|
|
2175
|
+
declare var wjMenuItemMeta: IWjComponentMeta;
|
|
2176
|
+
export { wjMenuItemMeta };
|
|
2177
|
+
/**
|
|
2178
|
+
* Angular 2 directive for {@link wijmo.angular2legacy.input.WjMenu} items.
|
|
2179
|
+
*
|
|
2180
|
+
* The <b>wj-menu-item</b> component must be
|
|
2181
|
+
* contained in a {@link wijmo.angular2legacy.input.WjMenu} component.
|
|
2182
|
+
*
|
|
2183
|
+
* Use the <b>wj-menu-item</b> component to add <b></b> controls to your
|
|
2184
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
2185
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
2186
|
+
*/
|
|
2187
|
+
export declare class WjMenuItem implements OnInit, OnDestroy, AfterViewInit {
|
|
2188
|
+
private viewContainerRef;
|
|
2189
|
+
value: any;
|
|
2190
|
+
cmd: any;
|
|
2191
|
+
cmdParam: any;
|
|
2192
|
+
header: string;
|
|
2193
|
+
_ownerMenu: wjcInput.Menu;
|
|
2194
|
+
templateDir: WjMenuItemTemplateDir;
|
|
2195
|
+
contentRoot: HTMLElement;
|
|
2196
|
+
static readonly meta: IWjComponentMetadata;
|
|
2197
|
+
private _wjBehaviour;
|
|
2198
|
+
/**
|
|
2199
|
+
* Indicates whether the component has been initialized by Angular.
|
|
2200
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
2201
|
+
*/
|
|
2202
|
+
isInitialized: boolean;
|
|
2203
|
+
/**
|
|
2204
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
2205
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
2206
|
+
*/
|
|
2207
|
+
initialized: EventEmitter<any>;
|
|
2208
|
+
/**
|
|
2209
|
+
* Gets or sets a name of a property that this component is assigned to.
|
|
2210
|
+
* Default value is 'itemsSource'.
|
|
2211
|
+
*/
|
|
2212
|
+
wjProperty: string;
|
|
2213
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any, viewContainerRef: ViewContainerRef);
|
|
2214
|
+
/**
|
|
2215
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
2216
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
2217
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
2218
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
2219
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
2220
|
+
*/
|
|
2221
|
+
created(): void;
|
|
2222
|
+
ngOnInit(): void;
|
|
2223
|
+
ngAfterViewInit(): void;
|
|
2224
|
+
ngOnDestroy(): void;
|
|
2225
|
+
added(toItem: HTMLElement): void;
|
|
2226
|
+
}
|
|
2227
|
+
export declare class WjMenuItemTemplateDir implements ngCore.AfterContentInit {
|
|
2228
|
+
viewContainerRef: ViewContainerRef;
|
|
2229
|
+
templateRef: TemplateRef<any>;
|
|
2230
|
+
elRef: ElementRef;
|
|
2231
|
+
wjMenuItemTemplateDir: any;
|
|
2232
|
+
ownerItem: WjMenuItem;
|
|
2233
|
+
contentRoot: HTMLElement;
|
|
2234
|
+
constructor(viewContainerRef: ViewContainerRef, templateRef: TemplateRef<any>, elRef: ElementRef, injector: Injector, menuItem: WjMenuItem, menuSeparator: WjMenuSeparator);
|
|
2235
|
+
ngAfterContentInit(): void;
|
|
2236
|
+
}
|
|
2237
|
+
declare var wjMenuSeparatorMeta: IWjComponentMeta;
|
|
2238
|
+
export { wjMenuSeparatorMeta };
|
|
2239
|
+
/**
|
|
2240
|
+
* Angular 2 directive for {@link wijmo.angular2legacy.input.WjMenu} item separators.
|
|
2241
|
+
*
|
|
2242
|
+
* The <b>wj-menu-separator</b> component must be
|
|
2243
|
+
* contained in a {@link wijmo.angular2legacy.input.WjMenu} component.
|
|
2244
|
+
*
|
|
2245
|
+
* Use the <b>wj-menu-separator</b> component to add <b></b> controls to your
|
|
2246
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
2247
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
2248
|
+
*/
|
|
2249
|
+
export declare class WjMenuSeparator extends WjMenuItem implements OnInit, OnDestroy, AfterViewInit {
|
|
2250
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any, viewContainerRef: ViewContainerRef);
|
|
2251
|
+
added(toItem: HTMLElement): void;
|
|
2252
|
+
}
|
|
2253
|
+
declare var wjItemTemplateMeta: IWjDirectiveMeta;
|
|
2254
|
+
export { wjItemTemplateMeta };
|
|
2255
|
+
/**
|
|
2256
|
+
* Angular 2 directive for item templates of item list components.
|
|
2257
|
+
*
|
|
2258
|
+
* The <b>[wjItemTemplate]</b> directive must be
|
|
2259
|
+
* contained in one of the following components:
|
|
2260
|
+
* {@link wijmo.angular2legacy.input.WjListBox}
|
|
2261
|
+
* , {@link wijmo.angular2legacy.input.WjMenu}
|
|
2262
|
+
* , {@link wijmo.angular2legacy.input.WjComboBox}
|
|
2263
|
+
* or {@link wijmo.angular2legacy.input.WjMultiSelect}.
|
|
2264
|
+
*
|
|
2265
|
+
* The <b>[wjItemTemplate]</b> directive defines a template for items of a component
|
|
2266
|
+
* that it's nested in.
|
|
2267
|
+
* The template may contain an arbitrary HTML fragment with Angular 2 bindings and directives.
|
|
2268
|
+
* The local <b>item</b>, <b>itemIndex</b> and <b>control</b> template variables can be used in Angular 2
|
|
2269
|
+
* bindings that refer to the data item, its index, and the owner control. For example:
|
|
2270
|
+
*
|
|
2271
|
+
*<pre><wj-list-box style="max-height:300px;width:250px;"
|
|
2272
|
+
* [itemsSource]="musicians">
|
|
2273
|
+
* <ng-template wjItemTemplate let-item="item" let-itemIndex="itemIndex">
|
|
2274
|
+
* {​{itemIndex + 1}}. <b>{​{item.name}}</b>
|
|
2275
|
+
* <div *ngIf="item.photo">
|
|
2276
|
+
* <img [src]="item.photo" height="100" />
|
|
2277
|
+
* <br />
|
|
2278
|
+
* <a href="https://www.google.com/#newwindow=1&q=The+Beatles+"
|
|
2279
|
+
* target="_blank"
|
|
2280
|
+
* style="color:red">go there!</a>
|
|
2281
|
+
* </div>
|
|
2282
|
+
* </ng-template>
|
|
2283
|
+
* </wj-list-box></pre>
|
|
2284
|
+
*/
|
|
2285
|
+
export declare class WjItemTemplate implements OnInit, OnDestroy, AfterViewInit {
|
|
2286
|
+
viewContainerRef: ViewContainerRef;
|
|
2287
|
+
templateRef: TemplateRef<any>;
|
|
2288
|
+
wjItemTemplate: any;
|
|
2289
|
+
ownerControl: wjcCore.Control;
|
|
2290
|
+
listBox: wjcInput.ListBox;
|
|
2291
|
+
private _cdRef;
|
|
2292
|
+
static readonly meta: IWjComponentMetadata;
|
|
2293
|
+
private _wjBehaviour;
|
|
2294
|
+
/**
|
|
2295
|
+
* Indicates whether the component has been initialized by Angular.
|
|
2296
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
2297
|
+
*/
|
|
2298
|
+
isInitialized: boolean;
|
|
2299
|
+
/**
|
|
2300
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
2301
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
2302
|
+
*/
|
|
2303
|
+
initialized: EventEmitter<any>;
|
|
2304
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any, viewContainerRef: ViewContainerRef, templateRef: TemplateRef<any>, cdRef: ChangeDetectorRef);
|
|
2305
|
+
/**
|
|
2306
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
2307
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
2308
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
2309
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
2310
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
2311
|
+
*/
|
|
2312
|
+
created(): void;
|
|
2313
|
+
ngOnInit(): void;
|
|
2314
|
+
ngAfterViewInit(): void;
|
|
2315
|
+
ngOnDestroy(): void;
|
|
2316
|
+
private _attachToControl;
|
|
2317
|
+
private _loadingItems;
|
|
2318
|
+
private _fmtItem;
|
|
2319
|
+
private _instantiateTemplate;
|
|
2320
|
+
private static _getListBox;
|
|
2321
|
+
}
|
|
2322
|
+
declare var wjPopupMeta: IWjComponentMeta;
|
|
2323
|
+
export { wjPopupMeta };
|
|
2324
|
+
/**
|
|
2325
|
+
* Angular 2 component for the {@link wijmo.input.Popup} control.
|
|
2326
|
+
*
|
|
2327
|
+
* Use the <b>wj-popup</b> component to add <b>Popup</b> controls to your
|
|
2328
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
2329
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
2330
|
+
*
|
|
2331
|
+
* The <b>WjPopup</b> component is derived from the <b>Popup</b> control and
|
|
2332
|
+
* inherits all its properties, events and methods.
|
|
2333
|
+
*/
|
|
2334
|
+
export declare class WjPopup extends wjcInput.Popup implements OnInit, OnDestroy, AfterViewInit, OnChanges {
|
|
2335
|
+
static readonly meta: IWjComponentMetadata;
|
|
2336
|
+
private _wjBehaviour;
|
|
2337
|
+
/**
|
|
2338
|
+
* Indicates whether the component has been initialized by Angular.
|
|
2339
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
2340
|
+
*/
|
|
2341
|
+
isInitialized: boolean;
|
|
2342
|
+
/**
|
|
2343
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
2344
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
2345
|
+
*/
|
|
2346
|
+
initialized: EventEmitter<any>;
|
|
2347
|
+
/**
|
|
2348
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
2349
|
+
* Default value is ''.
|
|
2350
|
+
*/
|
|
2351
|
+
wjModelProperty: string;
|
|
2352
|
+
/**
|
|
2353
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
2354
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2355
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
2356
|
+
*/
|
|
2357
|
+
gotFocusNg: EventEmitter<any>;
|
|
2358
|
+
/**
|
|
2359
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
2360
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2361
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
2362
|
+
*/
|
|
2363
|
+
lostFocusNg: EventEmitter<any>;
|
|
2364
|
+
/**
|
|
2365
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
2366
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2367
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
2368
|
+
*/
|
|
2369
|
+
refreshingNg: EventEmitter<any>;
|
|
2370
|
+
/**
|
|
2371
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
2372
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2373
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
2374
|
+
*/
|
|
2375
|
+
refreshedNg: EventEmitter<any>;
|
|
2376
|
+
/**
|
|
2377
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
2378
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2379
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
2380
|
+
*/
|
|
2381
|
+
invalidInputNg: EventEmitter<any>;
|
|
2382
|
+
/**
|
|
2383
|
+
* Angular (EventEmitter) version of the Wijmo <b>showing</b> event for programmatic access.
|
|
2384
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2385
|
+
* In template bindings use the conventional <b>showing</b> Wijmo event name.
|
|
2386
|
+
*/
|
|
2387
|
+
showingNg: EventEmitter<any>;
|
|
2388
|
+
/**
|
|
2389
|
+
* Angular (EventEmitter) version of the Wijmo <b>shown</b> event for programmatic access.
|
|
2390
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2391
|
+
* In template bindings use the conventional <b>shown</b> Wijmo event name.
|
|
2392
|
+
*/
|
|
2393
|
+
shownNg: EventEmitter<any>;
|
|
2394
|
+
/**
|
|
2395
|
+
* Angular (EventEmitter) version of the Wijmo <b>hiding</b> event for programmatic access.
|
|
2396
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2397
|
+
* In template bindings use the conventional <b>hiding</b> Wijmo event name.
|
|
2398
|
+
*/
|
|
2399
|
+
hidingNg: EventEmitter<any>;
|
|
2400
|
+
/**
|
|
2401
|
+
* Angular (EventEmitter) version of the Wijmo <b>hidden</b> event for programmatic access.
|
|
2402
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2403
|
+
* In template bindings use the conventional <b>hidden</b> Wijmo event name.
|
|
2404
|
+
*/
|
|
2405
|
+
hiddenNg: EventEmitter<any>;
|
|
2406
|
+
/**
|
|
2407
|
+
* Angular (EventEmitter) version of the Wijmo <b>resizing</b> event for programmatic access.
|
|
2408
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2409
|
+
* In template bindings use the conventional <b>resizing</b> Wijmo event name.
|
|
2410
|
+
*/
|
|
2411
|
+
resizingNg: EventEmitter<any>;
|
|
2412
|
+
/**
|
|
2413
|
+
* Angular (EventEmitter) version of the Wijmo <b>sizeChanging</b> event for programmatic access.
|
|
2414
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2415
|
+
* In template bindings use the conventional <b>sizeChanging</b> Wijmo event name.
|
|
2416
|
+
*/
|
|
2417
|
+
sizeChangingNg: EventEmitter<any>;
|
|
2418
|
+
/**
|
|
2419
|
+
* Angular (EventEmitter) version of the Wijmo <b>sizeChanged</b> event for programmatic access.
|
|
2420
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2421
|
+
* In template bindings use the conventional <b>sizeChanged</b> Wijmo event name.
|
|
2422
|
+
*/
|
|
2423
|
+
sizeChangedNg: EventEmitter<any>;
|
|
2424
|
+
/**
|
|
2425
|
+
* Angular (EventEmitter) version of the Wijmo <b>resized</b> event for programmatic access.
|
|
2426
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2427
|
+
* In template bindings use the conventional <b>resized</b> Wijmo event name.
|
|
2428
|
+
*/
|
|
2429
|
+
resizedNg: EventEmitter<any>;
|
|
2430
|
+
/**
|
|
2431
|
+
* Angular (EventEmitter) version of the Wijmo <b>dragging</b> event for programmatic access.
|
|
2432
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2433
|
+
* In template bindings use the conventional <b>dragging</b> Wijmo event name.
|
|
2434
|
+
*/
|
|
2435
|
+
draggingNg: EventEmitter<any>;
|
|
2436
|
+
/**
|
|
2437
|
+
* Angular (EventEmitter) version of the Wijmo <b>positionChanging</b> event for programmatic access.
|
|
2438
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2439
|
+
* In template bindings use the conventional <b>positionChanging</b> Wijmo event name.
|
|
2440
|
+
*/
|
|
2441
|
+
positionChangingNg: EventEmitter<any>;
|
|
2442
|
+
/**
|
|
2443
|
+
* Angular (EventEmitter) version of the Wijmo <b>positionChanged</b> event for programmatic access.
|
|
2444
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2445
|
+
* In template bindings use the conventional <b>positionChanged</b> Wijmo event name.
|
|
2446
|
+
*/
|
|
2447
|
+
positionChangedNg: EventEmitter<any>;
|
|
2448
|
+
/**
|
|
2449
|
+
* Angular (EventEmitter) version of the Wijmo <b>dragged</b> event for programmatic access.
|
|
2450
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2451
|
+
* In template bindings use the conventional <b>dragged</b> Wijmo event name.
|
|
2452
|
+
*/
|
|
2453
|
+
draggedNg: EventEmitter<any>;
|
|
2454
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
2455
|
+
/**
|
|
2456
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
2457
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
2458
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
2459
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
2460
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
2461
|
+
*/
|
|
2462
|
+
created(): void;
|
|
2463
|
+
ngOnInit(): void;
|
|
2464
|
+
ngAfterViewInit(): void;
|
|
2465
|
+
ngOnDestroy(): void;
|
|
2466
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
2467
|
+
ngOnChanges(changes: {
|
|
2468
|
+
[key: string]: ngCore.SimpleChange;
|
|
2469
|
+
}): void;
|
|
2470
|
+
dispose(): void;
|
|
2471
|
+
}
|
|
2472
|
+
/**
|
|
2473
|
+
* Angular 2 directive for context menus.
|
|
2474
|
+
*
|
|
2475
|
+
* Use the <b>wjContextMenu</b> directive to add context menus to elements
|
|
2476
|
+
* on the page. The wjContextMenu directive is based on the <b>wj-menu</b>
|
|
2477
|
+
* component; it displays a popup menu when the user performs a context menu
|
|
2478
|
+
* request on an element (usually a right-click).
|
|
2479
|
+
*
|
|
2480
|
+
* The wjContextMenu directive is specified as a parameter added to the
|
|
2481
|
+
* element that the context menu applies to. The parameter value is a
|
|
2482
|
+
* reference to the <b>wj-menu</b> component. For example:
|
|
2483
|
+
*
|
|
2484
|
+
* <pre><!-- paragraph with a context menu -->
|
|
2485
|
+
*<p [wjContextMenu]="menu" >
|
|
2486
|
+
* This paragraph has a context menu.</p>
|
|
2487
|
+
*
|
|
2488
|
+
*<!-- define the context menu (hidden and with an id) -->
|
|
2489
|
+
*<wj-menu #menu style="display:none">
|
|
2490
|
+
* <wj-menu-item [cmd]="cmdOpen" [cmdParam] ="1">Open...</wj-menu-item>
|
|
2491
|
+
* <wj-menu-item [cmd]="cmdSave" [cmdParam]="2">Save </wj-menu-item>
|
|
2492
|
+
* <wj-menu-item [cmd]="cmdSave" [cmdParam]="3">Save As...</wj-menu-item>
|
|
2493
|
+
* <wj-menu-item [cmd]="cmdNew" [cmdParam] ="4">New...</wj-menu-item>
|
|
2494
|
+
* <wj-menu-separator></wj-menu-separator>
|
|
2495
|
+
* <wj-menu-item [cmd]="cmdExit" [cmdParam]="5">Exit</wj-menu-item>
|
|
2496
|
+
*</wj-menu ></pre>
|
|
2497
|
+
*/
|
|
2498
|
+
export declare class WjContextMenu {
|
|
2499
|
+
private elRef;
|
|
2500
|
+
wjContextMenu: wjcInput.Menu;
|
|
2501
|
+
constructor(elRef: ElementRef);
|
|
2502
|
+
onContextMenu(e: MouseEvent): void;
|
|
2503
|
+
}
|
|
2504
|
+
declare var wjCollectionViewNavigatorMeta: IWjComponentMeta;
|
|
2505
|
+
export { wjCollectionViewNavigatorMeta };
|
|
2506
|
+
/**
|
|
2507
|
+
* Angular 2 component for the {@link wijmo.input.CollectionViewNavigator} control.
|
|
2508
|
+
*
|
|
2509
|
+
* Use the <b>wj-collection-view-navigator</b> component to add <b>CollectionViewNavigator</b> controls to your
|
|
2510
|
+
* Angular 2 applications. For details about Angular 2 markup syntax, see
|
|
2511
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>.
|
|
2512
|
+
*
|
|
2513
|
+
* The <b>WjCollectionViewNavigator</b> component is derived from the <b>CollectionViewNavigator</b> control and
|
|
2514
|
+
* inherits all its properties, events and methods.
|
|
2515
|
+
*/
|
|
2516
|
+
export declare class WjCollectionViewNavigator extends wjcInput.CollectionViewNavigator implements OnInit, OnDestroy, AfterViewInit {
|
|
2517
|
+
static readonly meta: IWjComponentMetadata;
|
|
2518
|
+
private _wjBehaviour;
|
|
2519
|
+
/**
|
|
2520
|
+
* Indicates whether the component has been initialized by Angular.
|
|
2521
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
2522
|
+
*/
|
|
2523
|
+
isInitialized: boolean;
|
|
2524
|
+
/**
|
|
2525
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
2526
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
2527
|
+
*/
|
|
2528
|
+
initialized: EventEmitter<any>;
|
|
2529
|
+
/**
|
|
2530
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
2531
|
+
* Default value is ''.
|
|
2532
|
+
*/
|
|
2533
|
+
wjModelProperty: string;
|
|
2534
|
+
/**
|
|
2535
|
+
* Angular (EventEmitter) version of the Wijmo <b>gotFocus</b> event for programmatic access.
|
|
2536
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2537
|
+
* In template bindings use the conventional <b>gotFocus</b> Wijmo event name.
|
|
2538
|
+
*/
|
|
2539
|
+
gotFocusNg: EventEmitter<any>;
|
|
2540
|
+
/**
|
|
2541
|
+
* Angular (EventEmitter) version of the Wijmo <b>lostFocus</b> event for programmatic access.
|
|
2542
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2543
|
+
* In template bindings use the conventional <b>lostFocus</b> Wijmo event name.
|
|
2544
|
+
*/
|
|
2545
|
+
lostFocusNg: EventEmitter<any>;
|
|
2546
|
+
/**
|
|
2547
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshing</b> event for programmatic access.
|
|
2548
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2549
|
+
* In template bindings use the conventional <b>refreshing</b> Wijmo event name.
|
|
2550
|
+
*/
|
|
2551
|
+
refreshingNg: EventEmitter<any>;
|
|
2552
|
+
/**
|
|
2553
|
+
* Angular (EventEmitter) version of the Wijmo <b>refreshed</b> event for programmatic access.
|
|
2554
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2555
|
+
* In template bindings use the conventional <b>refreshed</b> Wijmo event name.
|
|
2556
|
+
*/
|
|
2557
|
+
refreshedNg: EventEmitter<any>;
|
|
2558
|
+
/**
|
|
2559
|
+
* Angular (EventEmitter) version of the Wijmo <b>invalidInput</b> event for programmatic access.
|
|
2560
|
+
* Use this event name if you want to subscribe to the Angular version of the event in code.
|
|
2561
|
+
* In template bindings use the conventional <b>invalidInput</b> Wijmo event name.
|
|
2562
|
+
*/
|
|
2563
|
+
invalidInputNg: EventEmitter<any>;
|
|
2564
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
2565
|
+
/**
|
|
2566
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
2567
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
2568
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
2569
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
2570
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
2571
|
+
*/
|
|
2572
|
+
created(): void;
|
|
2573
|
+
ngOnInit(): void;
|
|
2574
|
+
ngAfterViewInit(): void;
|
|
2575
|
+
ngOnDestroy(): void;
|
|
2576
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
2577
|
+
}
|
|
2578
|
+
declare var wjCollectionViewPagerMeta: IWjComponentMeta;
|
|
2579
|
+
export { wjCollectionViewPagerMeta };
|
|
2580
|
+
/**
|
|
2581
|
+
* Obsolete. Use wj-collection-view-navigator with [byPage]="true" instead.
|
|
2582
|
+
*
|
|
2583
|
+
* Angular 2 component for an {@link ICollectionView} pager element.
|
|
2584
|
+
*
|
|
2585
|
+
* Use the <b>wj-collection-view-pager</b> component to add an element
|
|
2586
|
+
* that allows users to navigate through the pages in a paged {@link ICollectionView}.
|
|
2587
|
+
* For details about Angular 2 markup syntax, see
|
|
2588
|
+
* <a href="/wijmo/docs/GettingStarted/Angular-Components">Angular 2 Markup</a>. For example:
|
|
2589
|
+
*
|
|
2590
|
+
* <pre><wj-collection-view-pager
|
|
2591
|
+
* [cv]="myCollectionView">
|
|
2592
|
+
* </wj-collection-view-pager></pre>
|
|
2593
|
+
*/
|
|
2594
|
+
export declare class WjCollectionViewPager extends wjcInput.CollectionViewNavigator implements OnInit, OnDestroy, AfterViewInit {
|
|
2595
|
+
static readonly meta: IWjComponentMetadata;
|
|
2596
|
+
private _wjBehaviour;
|
|
2597
|
+
/**
|
|
2598
|
+
* Indicates whether the component has been initialized by Angular.
|
|
2599
|
+
* Changes its value from false to true right before triggering the <b>initialized</b> event.
|
|
2600
|
+
*/
|
|
2601
|
+
isInitialized: boolean;
|
|
2602
|
+
/**
|
|
2603
|
+
* This event is triggered after the component has been initialized by Angular, that is
|
|
2604
|
+
* all bound properties have been assigned and child components (if any) have been initialized.
|
|
2605
|
+
*/
|
|
2606
|
+
initialized: EventEmitter<any>;
|
|
2607
|
+
/**
|
|
2608
|
+
* Defines a name of a property represented by [(ngModel)] directive (if specified).
|
|
2609
|
+
* Default value is ''.
|
|
2610
|
+
*/
|
|
2611
|
+
wjModelProperty: string;
|
|
2612
|
+
constructor(elRef: ElementRef, injector: Injector, parentCmp: any);
|
|
2613
|
+
/**
|
|
2614
|
+
* If you create a custom component inherited from a Wijmo component, you can override this
|
|
2615
|
+
* method and perform necessary initializations that you usually do in a class constructor.
|
|
2616
|
+
* This method is called in the last line of a Wijmo component constructor and allows you
|
|
2617
|
+
* to not declare your custom component's constructor at all, thus preventing you from a necessity
|
|
2618
|
+
* to maintain constructor parameters and keep them in synch with Wijmo component's constructor parameters.
|
|
2619
|
+
*/
|
|
2620
|
+
created(): void;
|
|
2621
|
+
ngOnInit(): void;
|
|
2622
|
+
ngAfterViewInit(): void;
|
|
2623
|
+
ngOnDestroy(): void;
|
|
2624
|
+
addEventListener(target: EventTarget, type: string, fn: any, capture?: boolean): void;
|
|
2625
|
+
}
|
|
2626
|
+
export declare class WjInputModule {
|
|
2627
|
+
}
|