Make legend item of BarSeries reflect it's visual style. For example, if I'll make a BarSeries with a border like this:
<Style TargetType="Border">
<Setter Property="Background" Value="Transparent" />
<Setter Property="BorderThickness" Value="1" />
<Setter Property="BorderBrush" Value="{StaticResource chartRed}" />
</Style>
then there won't be a rectangle in a legend as expected (it will show a transparent one instead, without border).
REASON FOR DECLINATION:
The RadLegend is a standalone control which allows for customization of the legend item visuals (one can use the ItemTemplate property of the RadLegend to control the legend item's appearance or can retemplate the LegendItemControl). There is no direct link between the ChartView and the RadLegend control and the appearance of the legend elements can be done by framework means such as Style, DataTemplate and ControlTemplate. The suggested way of manipulating the look of the chart legend item is making use of the ItemTemplate property of the RadLegend and the MarkerGeometry property of the series legend settings.
Make easy way to set Stroke/Fill for all columns in a specific BarSeries. I know about DefaultVisualStyle, but it's too cumbersome to use. For example, Infragistics's chart has this. Just make use of properties like Background and Stroke. REASON FOR DECLINATION: We have decided to decline this feature request because the bar series can be styled via few different approaches, such as a chart palette, default visual style, default visual style selector, point template, point template selector. We consider the DefaultVisualStyle a very framework-friendly approach as it is easy to create and set up a style, in which you can manipulate any of the Border's properties, including adding Bindings to the actual business item.
Currently, when setting a style to a table/table cell the following syntax is imported properly
.tdborder{border: 1px solid black}
However, if the order of the properties is changed (solid 1px black), the style will not be interpreted.
The fix will be available in our latest LIB release (v. 2015.1.0323).
The value will be skipped when importing the document (<table width=200>). If the size is defined (px or %) as follows <table width=200px> or <table width=200%> then the width value will be respected. The fix is available in our latest LIB release (v. 2015.1.0316).
When document contains field element without the optional separator character, the import fails.
The fix is available in our latest LIB release (v. 2015.1.0316)
This item is migrated to the Telerik Document Processing portal: http://feedback.telerik.com/Project/184/Feedback/Details/190043 Please use the new item for commenting, voting and subscribing instead of this one.
In the XML all merged cells have the same content, instead of only the one visible having content and the rest being empty. This sometimes causes all cells to be visible in editors.
You can set the data of an image with the LoadFromUri event, but there is no way to set the size.
The feature will be available in our official release 2015 Q2.
The feature will be available in our official release 2015 Q2.
This item is migrated to the Telerik Document Processing portal: http://feedback.telerik.com/Project/184/Feedback/Details/190049 Please use the new item for commenting, voting and subscribing instead of this one.
These file formats are very similar to DOCX, and can be easily imported with loss of some information (e.g. macros). This item is migrated to the Telerik Document Processing portal: http://feedback.telerik.com/Project/184/Feedback/Details/190053 Please use the new item for commenting, voting and subscribing instead of this one.
When a document, which contains TOC with visible tab leader, is exported to PDF, the tab leader is missing in the produced document.
An InvalidCastException is thrown when reading the Trailer. The fix will be available in our latest LIB release (v. 2015.02.0810).
This item is migrated to the Telerik Document Processing portal: http://feedback.telerik.com/Project/184/Feedback/Details/190060 Please use the new item for commenting, voting and subscribing instead of this one.