-
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NSInternalInconsistencyException #27
Comments
@iBachek Morning. I am not sure why you did that modification in the first place - you wrapped each cell into a section. The Example app doesn't support more then one section. If you need more then one section - you will have to modify the other parts of the app. PS: About supplementary views in general see https://github.com/ekazaev/ChatLayout#about-supplementary-views |
@ekazaev section header has a visibility behavior when scrolling and snapping to the top, this is necessary to separate messages by date |
what parts do you mean? |
Firstly. This doesnt discount my comment above. If you want to have more then one section - you need to modify the rest of the app. Ill have a look. Secondly: Snapping header to the top is not supported by the layout itself. So if you need this behavior you'll need to implement it yourself. My assumption is that you need to create a fake date view at the top of the container view that will hold your collection view and track the visibility of the date cell within the collection view and if it is above the top boundary of the collection view - make your fake date view visible. See also #18 |
Hi, thank u for the new chat behaviour.
I faced with crash on your example app, you can reproduce it, if replace your code in
DefaultChatController
Reason: invalid number of sections. The number of sections contained in the collection view after the update (170) must be equal to the number of sections contained in the collection view before the update (89), plus or minus the number of sections inserted or deleted (0 inserted, 1 deleted).
change
line 147
to
The text was updated successfully, but these errors were encountered: