Hi,
it seems that the xamMonthView has an issue with manually added/changed appointments.
In our application the appointments are bound to an ObservableCollection of our own data class.If an user changes the start/end of an appointment, so that the duration is longer than one day, we have to create a new dataitem for each day.
To achieve this, we take the ActivityChanging Event, set "e.Cancel = true" and add the one dataitem per day to the ObservableCollection. But the xamMonthView displays all newly created apppointments at the last day of the given timespan.
For example, we have an appointment which is an all day event and starts at 12/09/2011 and the user sets the end of this appointment to 16/09/2011. The appointment now has a timespan of 4 days. After our modifications the xamMonthView shows the original appointment at 12/09/2011 and the 3 new created appointments at 15/09/2011 although all dataitems have the correct start and end dates.If we save this values and reload all lists and the current user, the values are displayed correctly.
Are we doing something wrong or is this a bug in the xamMonthView?
Thanks,Bastian
I'm not able to reproduce the behavior you're describing. Can you provide a sample that demonstrates the issue? Is it possible that you are not providing a unique Id to each new dataitem?
Thanks Andrew,
the unique id was the problem. They were all the same at this point because the dataitem is an entity object with an id generated by the database.
When I set the Id Property manually it works as expected.