Hi,
In TimeSlotCreated we do lot of processing on server and accordingly set the slot availibility.
In NavigationComplete we get the new visible dates from VisibleRangeStart and VisibleRangeEnd. If the VisibleRangeStart and VisibleRangeEnd changes i.e. if they are outside our cache data, we need to refresh our data and then set the slot availibility in TimeSlotCreated.
But we noticed that when user changes the date or moves back/forward using the navigation link, TimeSlotCreated is called before (with old dates) and after NavigationComplete event (with new dates).
Why TimeSlotCreated is called before NavigationComplete is called since the new dates are not set anyway?
Is there a way to prevent this? i.e. TimeSlotCreated gets called only after NavigationComplete? Or is there a way to get the new visible dates before TimeSlotCreated is called?
Thanks,
Abhijeet
In TimeSlotCreated we do lot of processing on server and accordingly set the slot availibility.
In NavigationComplete we get the new visible dates from VisibleRangeStart and VisibleRangeEnd. If the VisibleRangeStart and VisibleRangeEnd changes i.e. if they are outside our cache data, we need to refresh our data and then set the slot availibility in TimeSlotCreated.
But we noticed that when user changes the date or moves back/forward using the navigation link, TimeSlotCreated is called before (with old dates) and after NavigationComplete event (with new dates).
Why TimeSlotCreated is called before NavigationComplete is called since the new dates are not set anyway?
Is there a way to prevent this? i.e. TimeSlotCreated gets called only after NavigationComplete? Or is there a way to get the new visible dates before TimeSlotCreated is called?
Thanks,
Abhijeet