7 Answers, 1 is accepted
The current version of RadTimeBar does not support multiple selection. I will forward your feedback to our developers and in case other customers request this feature, we will consider implementing it.
Could you please elaborate a bit on the result you want to achieve with our control? In case I have a better overview of your requirement, I might be able to suggest a workaround that you can use for the time being.
Regards,
Tsvetie
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
Thank you for the followup. I will forward the additional information to our developers.
All the best,
Tsvetie
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
Ideally twoway bindable to filter descriptor from a "Date" column in a gridview.
Could you please describe your scenario in greater detail as well. The feature that Charlie asked about is selection within the selection and in case I understand you correctly, you have in mind something different - adjacent selected areas.
Greetings,Tsvetie
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
You are correct. We would like to use multiselection to be able to select for example year 2000 and year 2007 in the timebar (which might be showing data from 2000-2012).
The "same" data is also presented in a grid where we have a column that shows date and where the user can use the filter etc to see effects in other kind of visualizations (for example map, charts etc). In the grid it's very easy to select multiple
We would like to have the filter setting correspond to the timebar selection in a twoway binding so that when we change selection in the timebar the grid filter would update and vice versa (now we edit the filter manually and it works, but we miss the ability to multiselect in the timebar).
Btw: When we look in the sourcecode for the timebar we see a variable called IsCoercing... but no property for it...
We also experience difficulty when when using bindings to all the PeriodXXX, SelectionXXX, VisibleXXX since it seems to be hard to control what setting updates what (and when) (and the scrollbar doesn't reflect the changes we do on visibleXXX properties etc...). So now we create new timebars instead in codebehind whenever needed.
Thank you for the detailed information. I will forward it to our developers.
Regarding your last paragraph - I could not quite understand the problems that you have setting the period properties. Basically, there is a required precedence of the TimeBar's properties but in case you followed the instructions from the help topic, you should not experience any problems setting and updating those properties. In case you need additional help with that, please open a formal support ticket and send us a running test project, demonstrating the problem that you have.
Tsvetie
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>