-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[BUG] We lost swipes #1046
Comments
It was intentional because it causes conflicts with the "continue" function and causes data corruption. So swipes on generation have to be disabled as if during streaming. |
Man, this sucks... Do you plan to return this function? |
I need to plan it carefully so it doesn't break something else (last time it was overwriting the last swipe with a continue). |
I just updated from an older version. Generating a new message while reading previous ones was a critical feature for me, no other feature was worth loosing that functionality over. Without it you just halved(or worse) the speed I can use ST with. What am I supposed to do, copy/paste the old message first? At that point I'd be better off with a basic webui and a text box. And assuming everyone can just switch to streaming is a horrible development approach. |
I don't get it, swipes and streaming always worked well for me. What gives? I guess I'll just abstain from updating for now. |
I registered just to write this. I never use the "continue" function. I'm just used to generating and viewing large texts via swipes, leisurely reading and editing them, instead of constantly chatting in real time streaming in small pieces I can only ask you to fix this, please? |
Hello, mates.
It seems swipes function was broken somewhere in the last updates; we can't swipe anymore while we generate a new response, so we can't read the previous AI's output while generating another in background -> all the process takes more time.
Can it be fixed?
The text was updated successfully, but these errors were encountered: