I see a random issue in the charting component where the plot area doesn't always stretch(?) to the bottom bounds of the available area. I can't really figure out why it happens in some cases and not others. And it's random, sometimes it does it, sometimes not, which means maybe it's some timing issue? It generally fixes itself when I rotate the screen.
I also think it only happens when setting up the view programmatically using NSLayoutConstraints and visual format language.
Screenshot attached. In the example, you can see the X-Axis labels are in the correct position, but the plot area doesn't extend down to it all the time.
Any suggestions on some instance method to call, or an additional piece of code to fix this, or at least update the chart post-render so that it fills the entire area?
Using the latest SR, and I saw this issue in 7.1 and 8.1.
Hi Jeff,
Thank you for contacting Infragistics Developer Support.
I tried to reproduce this issue and everything works fine for me – even if I set NSLayoutConstraints the chart plot area is displayed properly. Can you please provide me with an isolated sample that reproduces the issue? I have attached the sample I used in order to test this for your reference and you can using as a starting point.
I am looking forward to your reply.
Thanks for the attached example. I was able to recreate the issue by modifying your example (attached).
The issue was that we don't create the series/datasourcehelper until post-load because we load data in the background. It was that fact that randomly caused the display issue. Even when attempting to solve the issue by creating a dummy series/datasourcehelper in viewDidLoad(), I had to add at least 2 dummy data points. When the post-load finally occurs, I remove the dummy series.
In the attached example, you can recreate the issue by commenting out the 2 lines that adds the 2nd dummy data point in viewDidLoad().
If you know of a better way to solve it, please let me know. However, I am happy to actually have figured out what the problem was and can at least fix it.
Jeff
An additional thought: Then again, I also do not see this random issue in the many other charts we use (but they don't use NSLayoutConstraints and visual format language) even though we follow the same pattern of not adding data until post-load. So maybe it's a combination of no initial data and NSLayoutConstraints? Don't know.
I wanted to let you know that we have just added a fix for this issue and it should be available in the next service release.
I also found that auto extent was largely contributing to the problem, so if you want a temporary workaround, you can set extent on both x and y axes to something like 20 and that should cause the chart to properly determine the correct plot area bounds.