I also gone through http://demos.telerik.com/silverlight/#DataFilter/CustomEditors.
Please assist.
3 Answers, 1 is accepted
Unfortunately, there can't be such and editor, since the data engine cannot handle "between". RadDataFilter can nest any number of filtering conditions, so you could easily create two filtering condition and combine them with AND -- that is the same as between.
Something like this.
Ross
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's DevProConnections Awards. We are competing in mind-blowing 20 categories and every vote counts! VOTE for Telerik NOW >>
If not, is there a way that you can make it so that we can subclass your operators, and create our own Is Between operator so that it can be added to the list of operators in the DataFilter so that our users can choose it.
Before you ask how am I planning on implementing it; I don't know yet. I just need to operator and will do whatever I need to for our users. We do not use the DataFilter to filter grids. We use is as a tool where users can specify criteria which we then convert into a query that is sent to the database.
We REALLY need this operator!
Thanks,
JD
Even if you could hack the control and add this operator, the LINQ data engine will not support it since it does not know what to do with it.
The entire data engine (which is shared between all of our data controls including RadGridView and RadDataFilter) relies on the FilterDescriptor class which has only a single Value. Even if we add such an operator, the existing infrastructure, i.e. you can only have one value editor per filter, will not allow the user to enter two separate values which are needed by the IsBetween operator.
In other words we would have to dump and re-write the data engine and RadGridView and RadDataFilter's filtering UI from scratch in order to support this custom operator.
Nevertheless, I will log your requirement as a feature request and if this feature generates enough interest among enough people, we will definitely consider its implementation even though that would mean a complete overhaul of the entire data engine logic.
Here you can vote for this feature.
Rossen Hristov
Telerik
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>