[SOLVED]Problems with "auto-forward" text speed

[AVNSnax]

I thought this might have been a legacy issue with Ren'Py 7.4, but it persists in 8.0.

I have this issue when, if you have auto-forward turned on, randomly there is no delay--dialog text displays and quickly advances to the next. This behavior occasionally happens in the regular game, but I can reproduce it whenever using multiple_say. The text for the left-hand column exhibits the display-and-quickly-disappear behavior, but the right-hand column operates as expected. The screens.rpy definition for both say windows is identical except for different styles for window placement.

I've been pouring over the Ren'Py code, and nothing immediately jumps out at me. Has anyone else seen this behavior? The (mostly) kinetic novel I'm working on lends itself to auto-forward, but these little glitches are irritating. The weirdest glitches are the few random lines where the behavior doesn't appear to change no matter what I change the text to. Thanks!

[AVNSnax]

I have this issue when, if you have auto-forward turned on, randomly there is no delay--dialog text displays and quickly advances to the next.

Well, I solved the random problem--it was a side-effect of python code running in a screen.

The multiple_say problem persists, though...

[AVNSnax]

RTFM. So auto-forward doesn't work on multiple character dialogue:

Auto-forward mode only works on the last block of text. While this should be fine in most cases, it can lead to problems if the last block of text is shorter than the rest, as auto-forward may engage early.

So, I'm back into "what-if" territory. I'm not even sure what the best approach should be in an instance like this. My VN has several points throughout the story where two characters are speaking to each other on the phone and I had planned on using multiple_say to handle it with a split-screen image. But auto-forward breaks it. Any suggestions on workarounds?

[PyTom]

Can you file an issue on github? This is almost certainly a problem with Ren'Py.

[AVNSnax]

That was fast. I downloaded 8.0.1 tonight, and you'd already fixed the problem. That's what I call customer service!

Now I wish I'd asked first instead of spending a couple of days trying to code a workaround.

Thanks, PyTom!