Is it possible that the VisibleRangeChanged event is not fired anymore when GroupFilter changes?
I do use a Viewmodel that implements a GroupFilter as well as a delegate for the VisibleRangeChangedCommand.
The delegate for VisibleRangeChangedCommand loads data from a database. When updating GroupFilter through the ViewModel in Q1 2011 VisibleRangeChangedCommand got called but this is not the case in Q2 2011.
.
2 Answers, 1 is accepted
You are correct, the VisibleRangeChangedCommand is not called anymore unless a property that affects the visible range is changed. Those properties are ActiveViewDefinition, DayEndTime, DayStartTime,
FirstDayOfWeek, VisibleDays and CurrentDate.
Why do you need to refresh the data when the GroupFilter property is changed? Probably there is a better place to do that?
Best wishes,
Valeri Hristov
the Telerik team
Register for the Q2 2011 What's New Webinar Week. Mark your calendar for the week starting July 18th and book your seat for a walk through of all the exciting stuff we will ship with the new release!
Rank 1
Thx Valery for the fast reply. The viewmodel reloads data when VisibleRange changes but also when GroupFilter changes. As GroupFilter changes did trigger the VisibleRangeChanged event, no further code to load data was needed and when initializing the ViewModel no call to get VisibleRange was needed.
I'll try to choose a different approach as things have changed.
Markus