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
{{ message }}
This repository has been archived by the owner on Aug 14, 2019. It is now read-only.
Took me many hours if not days to figure out why all my outgoing bubble messages appeared on the left side of screen as if they were incoming:
Finally I discovered that you need to set controller's self.sender to same value as you have in message sender! Then the message will appear as outgoing properly.
Thanks @romanr - This is already in the works, see #389.
Regarding the design:
The implicit distinction/comparison is actually much cleaner and nicer than having to track/set a separate BOOL value, which was a major shortcoming of v4.0 of this library. With the current design, the view is constructed directly from the model data -- not some arbitrary flag. If you compare the old v4.0 to the current build, you'll see how this is a more modular, flexible, and cleaner design.
However, as you noted - docs need to be better! #389 will be implemented soon! 👍
Took me many hours if not days to figure out why all my outgoing bubble messages appeared on the left side of screen as if they were incoming:
Finally I discovered that you need to set controller's self.sender to same value as you have in message sender! Then the message will appear as outgoing properly.
the code is in JSQMessagesViewController.m:
I think the best way would be is to add parameter to JSQMessage constructor like this:
The text was updated successfully, but these errors were encountered: