This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I am finding that there are issues with the x and Y axis for bar series and stacked bar series when plotting a string value; If there are less then 4 strings the axis displays duplicated items for the string values (please see attached). This is easily reproduced using the samples explorer project. Here are the steps:
We are using WPF Elements 5.1 May 29th overnight build. Thanks, Kamal |
|
|
Hello Kamal Thanks for bringing this to our attention. This issue will be resolved in the next nightly build. Jason Fauchelle |
|
|
Hi Jason, Thanks for the quick response. The issue was resolved in scenario when loading the graph however I can still reproduce as follows: I am using Actipro 3rd party control with docking windows. If I have a workspace displaying a stacked horizontal bar series graph and a validation tab/container on the same page that can be pinned then as soon as I pin the validation tab I see the same behavior as before where the string values are duplicated multiple times on the y axis. This only happens for the bar series graph. It appears that the same fix needs to be applied in this case/scenario Thanks, Kamal |
|
|
Hello Kamal I was unable to reproduce this, but I have put a fix in the most likely place causing this issue. This candidate fix will be available in the next nightly build. If the problem remains, please send a small repro project. Jason Fauchelle |
|
|
Hi Jason, It took us quite some time however we were finally able to reproduce the problem. It appears there is an issue with Loaded event of the user control getting fired twice but it will cause the plot to appear as per our demo last week. I was able to reproduce this by using tabs in the attached project and I suspect that it will likely occur with a regular WPF tab control as well. Anyhow, I have attached the test project.
I suspect if this gets fixed it will fix the problem in our software as well. Thanks. Kamal |
|
|
Hello Kamal Great work on creating a repro project. It looks like this issue has already been resolved! While working on the performance improvements over the last 2 days, I refactored the way that an important value used by the axis is updated. I was hoping that this would solve the issue, and was able to confirm this using the repro project. You can get the latest nightly build right now to see it resolved in your application. Jason Fauchelle |
|
|
Hi Jason, Great! I was able to confirm it is working properly in the test project I sent you. I am seeing a slightly different behavior when testing the software application however it may be something else. I will test more tomorrow to figure out what is happening but I think we can safely say that the original issue has been resolved. Thanks!! |
|
|
Hi Jason, Ok so I was able to reproduce the latest behavior we are experiencing in the attached test project. Again, the loaded event is getting fired twice and you can see the graph is cutting off the bars slightly when you click on the second tab. Thanks. |
|
|
Thanks for the repro project Kamal This issue will be resolved in the next nightly build. I'll explain what was going on here if you're interested: The way the axis labels are positioned are based on the LabelLayout property. Normal-layout starts the labels right at the start of the axis, this is great for charts like line series. Inside-layout is great for bar charts which pushes the labels inwards so that the bars are also pushed inwards and line up with the labels. You may have noticed that the layout is automatically selected based on what type of chart(s) you are displaying. But this value can also be set by developers, so we included logic to ignore this auto selection if the developer want's to set it themselves. Since there are several properties affected in this way, the easiest logic to implement was if the Minimum and Maximum properties have been set by a developer, then we say that the axis is NOT in auto mode. This in turn means that the LabelLayout property and others are not set automatically as it would most likely override the developers settings. When running your repro, it seems like the chart axis in the second tab is falling out of auto mode. The stack trace shows that both the minimum and maximum values are being set manually which as explained above switches off the auto LabelLayout logic. I've split this out so that each of these kinds of properties will handle it's own "is auto" logic. This will resolve this issue in the next nightly build. Jason Fauchelle |
|