Replies
If your dialog is a simple text box you can use the message property of the dialog instance in your typescript file. In the case of more involved templating you should just change the values inside the template before opening the dialog.
In the case of the provided sample above this will be:
ngAfterViewInit() {
this.dialog.message = '';
setTimeout(() => this.dialog.open(), 3000);
}
Hello Shailesh,
Thank you for contacting Infragistics Developer Support!
Yes, it is possible to toggle the dialog component from your typescript code. You only need to get a reference to it from your component and use the dialog API to manipulate it.
I have also made a sample which showcases a dialog opening 3 seconds after the component has loaded.
Hello Scott,
If the material icons are missing in your prod build, I suspect that there are not being bundled correctly with your application. Where are you "linking" them? Inside your styles, index.html or angular.json configuration?
A good practice is to put the material icon font files somewhere inside the src/assets directory of your project as the Angular CLI is configured to properly bundle/reference that folder when building/serving the app.
Hello,
The cellClassses property works a lot like the ngClass directive. It expects an object where the keys are the style classes that are to be applied and the values are either simple Boolean values or a callback that returns a Boolean value.
You can check out this sample where you can see it in action.
In your case it will be [cellClasses]="{'center-and-middle-text': true}"
Hello Singh,
Thank you for contacting Infragistics Developer Support!
In your case you can use the selectAll method of the combo i.e
However you would have to cancel the selectionChanging event. A better approach is to use a header template where you can place a button/checkbox/etc and call the selectAll method through the igCombo API.
For more information check: this and this and a sample showing off the header template feature
Hello Birendra,
I suspect the problem is due to your master page overriding the culture settings in your content pages.
I suggest you implement InitializeCulture() in your BasePage class and set it to your preferred local settings.
For additional information you can check out this thread
Feel free to contact me for further assistance.
Hello Birendra,
Thank you for contacting Infragistics Developer Support!
You should try setting EnableScriptGlobalization and EnableScriptLocalization off the ScriptManager to True.
For example:
<ig:WebScriptManager id="sm" runat="server" EnableScriptGlobalization="true" EnableScriptLocalization="true"></ig:WebScriptManager>