1.There are no analogical properties in the RadExpander in Q1 2012. We refactored its template in 2011, you can see the new template structure here
. However, you can send us your custom styles and we will help you to upgrade them.
2. Here you can find the list of breaking changes regarding filtering. We had to make them because we implemented filtering for our expression column which has no notion of Member. That is why we extracted all common logic for the two kinds of columns to the base abstract class OperatorValueFilterDescriptorBase.
Assuming that your column is a GridViewDataColumn, you have to different ways to get the Member.
A) Since this is an IColumnFilterDescriptor, you have a reference to the column so you can get Column.DataMemberBinding.Path.Path.
B) In case your column is a normal GridViewDataColumn (i.e. which has a DataMemberBinding), you can safely cast the abstract OperatorValueFilterDescriptorBase to a FilterDescriptor which has a Member.
In case your column is a GridViewExpressionColumn, you can safely cast the OperatorValueFilterDescriptorBase to a LambdaFilterDescriptor which has a LambdaExpression instead of a Member.
Long story short, we extracted everything except for the Member property from the FilterDescriptor class up to the base abstract OperatorValueFilterDescriptorBase class so that the new LambdaFilterDescriptor can derive from it and reuse its code.
We hope this helps.
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>