How to load the messages in the correct order using QMChatSectionManager.

[ajay2c9]

How to load the messages in the correct order using QMChatSectionManager.

Hi @ajay2c9 ,

We recommend you not to use QMChatSectionManager for your own Chat View Controller.

Unfortunately, there are some reasons:

1. We wrote it for using with our collection view.
2. Our collection view is transformed upside down.

That's why in your implementation you can get some unexpected behaviour.

[ajay2c9]

How to get the all messages at a time in a array in correct order without using the QMChatSectionManager and updating the array while sending and receiving the messages.

[Raikerian]

Hi @ajay2c9

First of all you are trying to use table view. So as I can understand you did not follow our guide here. You need to subclass from our QMChatViewController class in order to use all its features. With it you can easily customise such things as cells colours, font, size etc. As an example you can use our Q-municate project or Samples project. You can also use an example our new (development is in progress) Q-municate chat view controller customised class here (keep in mind, it is still under development).

In your current case unfortunately there is no a perfect way for you to use our custom section manager in your own table view. It was designed specially for our collection view been transformed upside down in order for new messages being displayed at the controller push. Thats why it is adding messages in incorrect order for you, but in a perfect order for us.

If you want to develop your own chat view controller based on table view you will need to design your own chat section manager (you can also read why collection view is better then table view for chat purposes).

You are also welcome to fork from our QMChatViewController repository and customise it fully inside. Our code is well documented in header files, so don't forget to read it :)

If you are still having questions feel free to ask.

[Raikerian]

@ajay2c9 If you are still having any other problems or questions - feel free to let us know by creating a separate issue.