When I plot an OHLCSeries or CandlestickSeries on a ChartView, sometimes I have data points where the open, high, low, and close values are all the same. In these cases, the data point doesn't show up at all -- no matter how far I may zoom in. It seems that I should at least be able to see some small visual indicator of where the data point is instead of it being completely invisible. This seems like a bug/usability issue, but I could be wrong. Is this behavior by design?
I'd like to request that such data points always be shown or that an option be provided to show them when each OHLC component value is the same. Thanks!
Paul
I'd like to request that such data points always be shown or that an option be provided to show them when each OHLC component value is the same. Thanks!
Paul
4 Answers, 1 is accepted
0
Hi Paul,
Thank you for pointing this. I definitely agree that an item should be shown, even all of the components (open, high, low, close) have the same value. So, I consider this a bug (logged here). For the time being you can workaround it by finding all Candlestick or OhlcShape elements and set their MinHeight property to 1:
Note that in order to use the ChildrenOfType extension method you should add "using Telerik.Windows.Controls".
Best regards,
Ves
the Telerik team
Thank you for pointing this. I definitely agree that an item should be shown, even all of the components (open, high, low, close) have the same value. So, I consider this a bug (logged here). For the time being you can workaround it by finding all Candlestick or OhlcShape elements and set their MinHeight property to 1:
void MyWindow_Loaded(object sender, RoutedEventArgs e) { foreach (var item in Chart1.ChildrenOfType<OhlcStick>()) { item.MinHeight = 1; } }Note that in order to use the ChildrenOfType extension method you should add "using Telerik.Windows.Controls".
Best regards,
Ves
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
Paul
Top achievements
Rank 1
Rank 1
answered on 07 Jan 2012, 08:34 AM
Ves,
I'm glad to hear you agree with my observation, and I appreciate you logging that bug report. I tried the work-around you proposed, and I implemented it in a manner that there left no room for any error on my part. However, I've not gotten it to work. I've set both the height and minheight to values much greater than 1, and I've confirmed (using Snoop) that the property values of the elements are indeed getting updated at runtime, and Snoop is even able to highlight for me where the element should be, and it even looks the right size. However, all such elements remain invisible; though I'm not sure why. Clearly, I'm missing something. Might you have any idea what's going on? I'm stumped!
Paul
I'm glad to hear you agree with my observation, and I appreciate you logging that bug report. I tried the work-around you proposed, and I implemented it in a manner that there left no room for any error on my part. However, I've not gotten it to work. I've set both the height and minheight to values much greater than 1, and I've confirmed (using Snoop) that the property values of the elements are indeed getting updated at runtime, and Snoop is even able to highlight for me where the element should be, and it even looks the right size. However, all such elements remain invisible; though I'm not sure why. Clearly, I'm missing something. Might you have any idea what's going on? I'm stumped!
Paul
0
Hi Paul,
The fix is included in the latest internal build, uploaded on Monday. Please, download it and give it a try. If the issue remains, please provide more details about your setup. Is there anything specific, is the chart populated on initial load? Or if possible -- you can send us a small example. Thanks.
Kind regards,
Ves
the Telerik team
The fix is included in the latest internal build, uploaded on Monday. Please, download it and give it a try. If the issue remains, please provide more details about your setup. Is there anything specific, is the chart populated on initial load? Or if possible -- you can send us a small example. Thanks.
Kind regards,
Ves
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
Paul
Top achievements
Rank 1
Rank 1
answered on 14 Jan 2012, 05:26 AM
Ves,
Thanks for informing me of the latest build containing a fix for this; I'm sorry I didn't get to test this sooner.
After testing the latest development build (2011.3.1309.40), I am still seeing the exact same problem I noticed earlier.
To make it easier for you to see exactly what I'm seeing, I have a VS solution you can check out. I just created a support ticket so I could post this solution; see thread 501478. Thanks!
Paul
Thanks for informing me of the latest build containing a fix for this; I'm sorry I didn't get to test this sooner.
After testing the latest development build (2011.3.1309.40), I am still seeing the exact same problem I noticed earlier.
To make it easier for you to see exactly what I'm seeing, I have a VS solution you can check out. I just created a support ticket so I could post this solution; see thread 501478. Thanks!
Paul