src/components/kendoUI/baseComponents/custom-container/custom-container.component.ts
selector | wm-custom-control-container |
styleUrls | ./custom-container.component.scss |
templateUrl | ./custom-container.component.html |
Properties |
Methods |
|
Inputs |
constructor(diff: KeyValueDiffers, service: WebMapService)
|
|||||||||
Parameters :
|
containerParent |
Type : string
|
Input of customcontrolcontainer component This is the name of the current tabcontrol that contains the tabpage component |
controlType |
Type : string
|
windowModel |
Type : any
|
This should be the current window model since the components that are defined inside a control are directly referenced by the window model, so in order to be successfully retrieved then the model associated to the custom control component must be the same window model. |
Protected addControl | ||||||||
addControl(id: string)
|
||||||||
Adds control Overrides the original functionality to load a generated components Containers are now generated as individual components in the migrated application this component should look up for them and load into the corresponding site automatically.
Parameters :
Returns :
void
|
Private getComponentKey | ||||||||
getComponentKey(model: any)
|
||||||||
Function to return a DataTransfer standard for each different mapperId as needed.
Parameters :
Returns :
string
|
Protected loadComponentCustom | ||||||||||||||||||||
loadComponentCustom(id: string, componentToLoad: any, model: any, windowModel: any)
|
||||||||||||||||||||
Loads the control component to the respective controlcontainer. Similar behavior than the BaseComponents loadComponent. The difference is for the newly individual components who needs the windowModel to be set.
Parameters :
Returns :
void
|
individualComponent |
Type : boolean
|
Local property to be used as a flag on LoadComponent method. It will be true for the custom components and false for any other component loaded dynamically. |