You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And when this mnCalendarView property is assigned through IB, then the dayCellClass property setting has no effect, because internally, the collection view has the classes already registered. I fixed this by adding an additional setter within MNCalendarView as follows:
I ran into this issue as well, however I searched the code and saw it was all being registered in the method registerUICollectionViewClasses(), so I just called that method myself after I set my custom class. Not sure what the advantages/disadvantages are to either approach. Mine is one less method, but yours is straight forward.
Given my code looks like this:
And when this mnCalendarView property is assigned through IB, then the dayCellClass property setting has no effect, because internally, the collection view has the classes already registered. I fixed this by adding an additional setter within
MNCalendarView
as follows:This simply overwrites the current cell class setting for the collection view.
Still thinking of a better way, but perhaps I will go ahead and submit a PR (for this and the other 2 getters)? Happy to get opinions on this.
The text was updated successfully, but these errors were encountered: