-
Notifications
You must be signed in to change notification settings - Fork 2
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
'typing' dots being displaced inwards #81
Comments
ah hm i notice this from time to time: I remember this issue existing already but perhaps we thought it went away. I think maybe first noticed this a few weeks ago? |
ahh this is very elusive - it only seems to happen when the bot double-texts (never when it's the first response to a user message). When did you add that functionality? |
it's been there for a couple of months, but we're using it more now -- when there's punctuation in a bot's response, it splits the message in two and adds it to bot queue. It doesn't use anything special though: everything just goes through the bot queue. recently I added in a 'line break' character that allows the bot to text over multiple lines without having punctuation to split them, which is probably why we're seeing this more. |
ohhh ok great thats helpful - yes the \n can totally be the culprit here |
ahhh it's not a \n though -- it's just appending 2 messages to the queue separately |
hmmmmmmm.... what it does is splits the sentence into an array, and concatenates that to the bot queue... which is maybe not quite the same
|
so the regex is looking for punctuation, or the 'newline' character |
ok I will play a bit with that and report back |
yeah. there's also one tiny hack that I did to make the bot dots appear at the start of rounds (they only get appended once there are messages on the screen) that just appends a blank message, before the bot starts typing. but the dots aren't distorted underneath that I don't think (+ I feel like we'd already seen the dots getting displaced before that...) that's done here:
|
^ very likely this is the reason, but I'm also investigating whether the |
@agnescameron any clues as to when that started?
The text was updated successfully, but these errors were encountered: