Nip draw in wrong position about bubble

[danielthomasdev]

Same issue, but I have some more info. I'm using code from the example with listview.builder - I've noticed it only does it when the message is the SAME as a previous message sent from the other user, so if user 1 sends Test and then user 2 sends Test, it flips the nip for user 2. Also, if you scroll up the listview and then back down the nip now faces the correct position.

[shinriyo]

enum BubbleNip { no, leftTop, leftBottom, rightTop, rightBottom }
I want other position.

[pazhut]

Had you looked at the screenshots? They are getting drawn on the left when they supposed to be on the right and vice versa

…

On Fri, Apr 17, 2020, 7:54 PM shinriyo ***@***.***> wrote: enum BubbleNip { no, leftTop, leftBottom, rightTop, rightBottom } I want other position. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#13 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANFZIGNSJPTKNBNRTERI7QLRNDT3JANCNFSM4MK2JPXA> .

[Rouvo]

Same issue, but I have some more info. I'm using code from the example with listview.builder - I've noticed it only does it when the message is the SAME as a previous message sent from the other user, so if user 1 sends Test and then user 2 sends Test, it flips the nip for user 2. Also, if you scroll up the listview and then back down the nip now faces the correct position.

Thanks for pointing this out. I just hit the same bug while using a listview and made the same observation about scrolling and changing the nip position. I was testing against a simple echo bot and this was driving me crazy.....now i just add a empty space behind the received message as a little work around.

I think I observed the same weird behaviour in another speech bubble library in the flutter web environment and thought it was the librarys fault btw. Still sticking to this one, because it looks much better.

[rh-id]

hi @vi-k , encounter the same issue, retest using the latest master branch and it seemed to solve the issue.

[vi-k]

See 1.2.1. I added key. Use it.