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
|
Hello Mindscape team, first of all I like your library. It works very fine, but I found an issue in LineSeries. Image of the bug see Bug.png attached How to reproduce the bug:
Does someone have this Problem too? It doesn't happen with Barchart. Actually I also replicated the LineSeries settings which were given by DashboardSample.sln. It also doesn't work. So, I guess it's a bug. Please guys can you fix it? I need it badly. My Chart definition:
Option 1:
Option 2:
|
|
|
Hello Maik Thanks for pointing out this issue and providing the clear repro steps. I have resolved the issue where the axis range was not updating correctly. The fix for this will be available through the next nightly build. The next nightly build will be available at around 1200 GMT (about 12 hours from now). You will be able to download the trial version of this from here: http://www.mindscapehq.com/products/wpfelements/nightly-builds Or go to your account page if you have a purchased copy: http://www.mindscapehq.com/store/myaccount I have not been able to reproduce the weird issue with line rendering. If this issue still remains after you have installed the next nightly build, make sure your data is being added in order along the X axis. The chart does not sort the data, so you will need to add each data point chronologically along the time axis. If your data is in fact ordered and the issue still remains, please send us a repro project so we can better find a solution. Also, I recommend that you use the DateTimeValueConverter along the X axis. I think you are doing this in your Option 1 code snippet. Jason Fauchelle |
|
|
Hello Jason, thanks for your awesome quick response. I gonna check your fix with the next nightly build. I made sure in advance that the Series contains chronologically ordered data because this was my first guess. I take your advice with DateTimeValueConverter and keep you posted if the bugfix worked. Bye Maik |
|
|
Hello Jason, great job, it works perfectly. Note: if you use
for XAxis the bug still occurs (you need to create 40 values Range:2009-2011 at first and then switch to a 40 value range starting from 2008-2011...) if I use Option 1, it works now. Edit: I played a bit around. if the propertys
for are not given, unfortunately the same issue occurs again. Cu Maik |
|
|
Hello Maik Unfortunately I have not been able to reproduce this issue. I have tested this when the Minimum and Maximum properties are not set and it seems to work as expected at my end. If this issue is a roadblock, please send us a simple repro project and we'll fix the issue for you as soon as possible. Jason Fauchelle |
|
|
Hello Jason, thanks for reply. The issues seems to be solved with your advice. So, no need for the moment to take further actions. I will provide a demo, if it changes. Thank you Maik |
|