I saw your post on the issues with the CollectionView and it's performance and I ran into the same issue with creating my own calendar control using a ContentView (on Android).
There can be 31 days in each individual control (rectangles) and then multiply that by 12 months plus the overlay label to show the day number and you get about 384 rendered items per calendar month. After binding this to the ItemSource in the CollectionView using an ObservableCollection, it will bring the app to its knees.
I feel like this isn't too much to ask, I'm sure people have done much more complicated controls. I'm not familiar with XCalendar, but any suggestions you have would be appreciated.
I saw your post on the issues with the
CollectionViewand it's performance and I ran into the same issue with creating my own calendar control using aContentView(on Android).There can be 31 days in each individual control (rectangles) and then multiply that by 12 months plus the overlay label to show the day number and you get about 384 rendered items per calendar month. After binding this to the
ItemSourcein theCollectionViewusing anObservableCollection, it will bring the app to its knees.I feel like this isn't too much to ask, I'm sure people have done much more complicated controls. I'm not familiar with
XCalendar, but any suggestions you have would be appreciated.