Hello Fatin,

My team and I have done an initial review of this forum thread, and it appears that there was an oversight – there should be a textStyle property on the igx-ring-series, but it is unfortunately and accidentally not exposed. More on that in a bit.

If possible, and if you are only using a single doughnut-chart ring, I would recommend upgrading to the igx-data-pie-chart control, which you can read about here: https://pt-br.infragistics.com/products/ignite-ui-angular/angular/components/charts/types/data-pie-chart. This, and the igx-pie-chart expose an innerExtent property that you can use to essentially make a doughnut chart, but the igx-data-pie-chart control is the successor to the igx-pie-chart. I noticed you stated that you are using Angular 16.1.29, but you will need to upgrade to a more recent version for the igx-data-pie-chart. This is documented here: https://pt-br.infragistics.com/products/ignite-ui-angular/angular/components/general-changelog-dv#1810-september-2024

You can use the following code with the igx-data-pie-chart to change the font size and make more of a “doughnut” shape:

<igx-data-pie-chart
name="chart"
#chart
[dataSource]="data"
calloutsTextStyle="20pt Verdana"
innerExtent="0.3">
</igx-data-pie-chart>

I have logged the missing textStyle property in our Ignite UI for Angular GitHub page, here: https://github.com/IgniteUI/igniteui-angular/issues/15293. I would recommend following this development item, as it will be updated when progress is made on it and a font style property is exposed. For the time being though, I would recommend continuing with the igx-data-pie-chart or igx-pie-chart.

Please let me know if you have any other questions or concerns on this matter.

Hello Cesar,

Thank you for your update on this matter. I am glad this worked to synchronize the widths of the chart.

Regarding the gridline synchronization, I would continue with the idea of keeping the minimum and maximum of the X-Axis the same. Since you can set the minimumValue and maximumValue in this case, it sounds like you are likely using an igx-numeric-x-axis, and so if you synchronize the values of those, you should be able to easily synchronize the gridlines.

Regarding the “actual” minimum/maximum value, these should only be used when you don’t explicitly set the minimumValue and maximumValue of the axis. There is also an actualVisible Minimum/Maximum value, which returns the values that are visible when zooming.

Please let me know if you have any other questions or concerns on this matter.

Hello Cesar,

I have been investigating into the behavior you are describing, and it sounds like you have multiple igx-data-chart components stacked vertically and you are essentially trying to synchronize them. My best recommendation in this case would be to first ensure that each chart is the same width, and then to utilize the labelExtent property of the igx-numeric-y-axis. This property determines the amount of space that a particular y-axis takes up as it determines the amount of space between the axis and the edge of the control.

If you have one chart with a single igx-numeric-y-axis and another with two, you can essentially synchronize the width of the x-axis by setting the labelExtent of the two y-axes and then setting it to the sum of those two labelExtents to the one y-axis. For example, if you set each of the two y-axes to labelExtent=30, you can set the labelExtent of the one to 60 have them take up the same amount of space.

Please let me know if you have any other questions or concerns on this matter.

Hello Nawfal,

For information about licensing and sales of Infragistics controls, my best recommendation would be to contact our sales department rather than posting on our forums. You can contact them using their contact information here: https://pt-br.infragistics.com/about-us/contact-us#sales.

Please let me know if you have any other questions or concerns on this matter.

Hello Mike,

Thank you for your update on this matter. I am glad you were able to resolve this issue by running Visual Studio in admin-mode.

As an aside to this, I personally have Visual Studio 2022 set to always open in admin mode, but as a test, I tried opening a solution with your Form in normal mode, but strangely still did not reproduce the issue.

Please let me know if you have any other questions or concerns on this matter.

Hello Michael,

I have included the sample Form and its designer into a new Windows Forms application on my end, and in doing so, I am able to load the designer without Visual Studio crashing with the error you are reporting. As proof, I am attaching a screenshot of what I see after including it on my end.

Since I am unable to reproduce the behavior, I have a few questions about your environment in this case. Can you please provide information on the following?

1. What is the specific version of Infragistics for Windows Forms 2020.2 that you are testing against? My tests were made against the latest service release in 20.2.20202.82. I also tested against the latest version of 22.2 and was not able to reproduce any error there.

2. What operating system is your machine running?

3. What version of the .NET Framework are you targeting? Judging by the error message, it looks like it’s probably 4.0, but I’m not certain on this.

Please let me know if you have any other questions or concerns on this matter.

Hello Sushmita,

I have been discussing this behavior with our development teams, and it appears that there could be a web security issue when trying to capture an image. This is not something that is specific to the IgxGeographicMap or the Ignite UI for Angular toolset, but as a potential fix to this, you can handle the DownloadingImage event on the map imagery and then set the image.crossOrigin property of the event arguments to “anonymous.” The following code can help you to achieve this:

let imagery : IgxOpenStreetMapImagery=  new IgxOpenStreetMapImagery();
imagery.i.downloadingImage = this.onDownloadingImage;       

this.map.backgroundContent = imagery;
—————-
public onDownloadingImage(sender: any, args: DownloadingMultiScaleImageEventArgs){
      args.image.crossOrigin = "anonymous";
}  

I hope this helps you. Please let me know if you have any other questions or concerns on this matter.