7 Answers, 1 is accepted
0
Hi Ming,
RadChart for Silverlight does not support the concept of series orientation as the ASP.NET control does and currently we have no concrete plans for its implementation -- instead it supports "horizontal" series types as first-class citizens on the SeriesDefinition level i.e. you can use HorizontalBar / HorizontalStackedBar / HorizontalStackedBar100 by choosing HorizontalSeriesDefinition / HorizontalStackedBarSeriesDefinition / HorizontalStackedBar100SeriesDefinition.
Hope this helps.
Best wishes,
Freddie
the Telerik team
RadChart for Silverlight does not support the concept of series orientation as the ASP.NET control does and currently we have no concrete plans for its implementation -- instead it supports "horizontal" series types as first-class citizens on the SeriesDefinition level i.e. you can use HorizontalBar / HorizontalStackedBar / HorizontalStackedBar100 by choosing HorizontalSeriesDefinition / HorizontalStackedBarSeriesDefinition / HorizontalStackedBar100SeriesDefinition.
Hope this helps.
Best wishes,
Freddie
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Ming
Top achievements
Rank 1
Rank 1
answered on 21 Jul 2010, 05:02 PM
Hi Freddie,
I was actually try to use the SeriesOrientation = Horizontal to archive the Scatter/Point with Logarithum on x-axis. right now RadChart support Logarithum on Y-axis however not x-axis, so I try to see if I can just set the SeriesOrientation to Horizontal to archive the result.
Thank you.
-Ming.
I was actually try to use the SeriesOrientation = Horizontal to archive the Scatter/Point with Logarithum on x-axis. right now RadChart support Logarithum on Y-axis however not x-axis, so I try to see if I can just set the SeriesOrientation to Horizontal to archive the result.
Thank you.
-Ming.
0
Hello Ming,
Indeed currently this scenario is not possible as AxisX does not support logarithmic mode. However, we have already logged this feature request in our public issue tracking system and it will be considered for one of the next versions of the control (you can vote for it here in order to increase its priority).
Regards,
Freddie
the Telerik team
Indeed currently this scenario is not possible as AxisX does not support logarithmic mode. However, we have already logged this feature request in our public issue tracking system and it will be considered for one of the next versions of the control (you can vote for it here in order to increase its priority).
Regards,
Freddie
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Andre
Top achievements
Rank 1
Rank 1
answered on 24 Mar 2011, 06:18 PM
Hi guys,
Any advance on AxisX supporting logarithmic mode?
Please, helpe me kick ChartFx out of our project and replace it with RadChart! Pleeease! :)
Cheers,
André
Any advance on AxisX supporting logarithmic mode?
Please, helpe me kick ChartFx out of our project and replace it with RadChart! Pleeease! :)
Cheers,
André
0
Hi Andre,
Thank you for contacting us.
Unfortunately this feature is still not available in the current version of the chart control. I will forward your inquiry to our devteam but it is unlikely that we will be able to add this to the current product backlog for the Q2 2011 release that is already under way.
Kind regards,
Giuseppe
the Telerik team
Thank you for contacting us.
Unfortunately this feature is still not available in the current version of the chart control. I will forward your inquiry to our devteam but it is unlikely that we will be able to add this to the current product backlog for the Q2 2011 release that is already under way.
Kind regards,
Giuseppe
the Telerik team
0
Andre
Top achievements
Rank 1
Rank 1
answered on 29 Mar 2011, 05:52 PM
Hi Giuseppe,
That's so sad...
I took a look at the source code and I could easily do it by myself extending the AxisX class.
BUT I can't. The framework has so many internal classes and methods that it's almost impossible to do something more elaborated.
In this case my problem is the AxisRange class (internal) and many internal or private methods in Axis and AxisX classes.
Please, if you can send a message to the development team, tell them this:
Ban the "internal" keyword from your source code. Also, make as many as possible virtual protected methods instead of private ones. Telerik is a framework for it's customers to use and extend to fit their needs. It's an AWESOME framework by the way and it would be much better if anyone could contribute and extend it's functionalities.
Cheers,
André Carlucci
That's so sad...
I took a look at the source code and I could easily do it by myself extending the AxisX class.
BUT I can't. The framework has so many internal classes and methods that it's almost impossible to do something more elaborated.
In this case my problem is the AxisRange class (internal) and many internal or private methods in Axis and AxisX classes.
Please, if you can send a message to the development team, tell them this:
Ban the "internal" keyword from your source code. Also, make as many as possible virtual protected methods instead of private ones. Telerik is a framework for it's customers to use and extend to fit their needs. It's an AWESOME framework by the way and it would be much better if anyone could contribute and extend it's functionalities.
Cheers,
André Carlucci
0
Bartholomeo Rocca
Top achievements
Rank 1
Rank 1
answered on 31 Mar 2011, 08:46 AM
Hello Andre,
I can see your reasoning (I have also wanted to extend the Telerik Framework sometimes and got stuck) but I see Telerik reasoning as well. Designing classes to be extensible isn't trivial, and inheritance isn't the single principle of OOP so sealed/internal preserves the developers intentions and makes their life easier. It allows the developer to control how the class is used, and allows them to make internal changes without worrying about breaking changes to code in the wild.
By any means if you have access to the source code, you can still to hack your way through ;).
Greetings,
Bart.
I can see your reasoning (I have also wanted to extend the Telerik Framework sometimes and got stuck) but I see Telerik reasoning as well. Designing classes to be extensible isn't trivial, and inheritance isn't the single principle of OOP so sealed/internal preserves the developers intentions and makes their life easier. It allows the developer to control how the class is used, and allows them to make internal changes without worrying about breaking changes to code in the wild.
By any means if you have access to the source code, you can still to hack your way through ;).
Greetings,
Bart.