[Solved] Readback.rpy and "extend"

[Levrex]

The problem is, when using a "text history" module (http://www.renpy.org/wiki/renpy/doc/coo ... xt_History), "extend" special character multiplies the line which it extends in text history.

I.e. the following example code:

Code: Select all

    n "\"Sup cutie,"
    extend " wanna ride in my car?\""

will give this:

"Sup cutie,"
"Sup cutie, wanna ride in my car?"

result in text history.

Is there a way to work this around?

[redeyesblackpanda]

I'd try this code:

Code: Select all

    "\"Sup cutie, {w}wanna ride in my car?\""

It should have the same effect, but not repeat. (Hopefully. I haven't tested it personally.)

[Levrex]

Well, i thought of that first, but that's ain't no option.
Click-to-continue indicator needs to be shown, otherwise it would seem strange and some unexperienced readers may think that the game is broken.

Of course, i can insert a click-to-continue anim.Filmstrip right into the line, but big novels tend to have many "extends", and that is too much time to waste and a bad optimisation.

[apricotorange]

I think the issue is just that ReadbackADVCharacter and ReadbackNVLCharacter defined there need to override do_extend. I'll take a closer look sometime soonish.

[Levrex]

Looking forward to, thanks!

[Samidarenina]

Actually, you can use "ctc_pause=" to set the CTC indicator to work with {w} and {p}.
Of course, if you need to show new pictures on the screen in the middle of the line, then you'll still need to use extend, but for the normal things, ctc_pause should do the thing.

(That being said, I stumbled across this thread for the exact same reason.)

[apricotorange]

Attaching a revised text history module; I stripped out a whole bunch of unnecessary stuff, and "extend" should work properly. Let me know if it works as expected.

[Levrex]

Holy heck, man, you are... you are... a man!
I expected that you'll just fix an "extend" bug, but you actually made it scrollable, just like i wanted to!!!
And yes, it works as expected.

Thank you very much.

Just one more thing, if i may ask...
If i want to divide the pages by some spaces (empty lines), should i add the code like this to NVLCharacter?
It's not that much necessary, but preferable.

Code: Select all

def do_nvl clear(self):
            add text "\n\n"
            super(ReadbackNVLCharacter, self).do_nvl clear()
            return

[apricotorange]

I didn't think I did anything which should affect the scrolling...

Slightly tweaked version: adds space after "nvl clear", and a bugfix to make it work properly across saves.

[Samidarenina]

I didn't think I did anything which should affect the scrolling...

Slightly tweaked version: adds space after "nvl clear", and a bugfix to make it work properly across saves.

I am sure this is asking for too much, but I'll try anyway.
Would you have a bit of time on your hands to also fix "extend" in the NVL page version you did for me some while ago in http://lemmasoft.renai.us/forums/viewto ... =8&t=15728? For now, it works perfectly, but the only problem I have is the extend not working.
I did try combining those 2 codes myself, but I keep getting an error.
Of course, you'd get a credits mention (again).


*crosses fingers and waits*

[Levrex]

I didn't think I did anything which should affect the scrolling...

Slightly tweaked version: adds space after "nvl clear", and a bugfix to make it work properly across saves.

Now i'm happy.
Thank you again!

[apricotorange]

Attaching combined version which supports both scrolling and "paged" variants, for Samidarenina.

[Samidarenina]

Ah, thank you so very much, Apricotorange. This is incredibly helpful to me.

[Levrex]

After some use, i noticed that blocking "rollback" key (assigning it to NullAction) for yesno_prompt screen won't work with readback.rpy. Because readback module overwrites the function of that key, but it overwrites that function on top of everything, which would be unwanted in my case.

I.e. i make the yesno_prompt show up while in "nvl" screen and it's supposed not to disappear until the user makes a decision, but if i roll back, going to the "text history" screen, i can watch the text history, call game menu, call prompt again, etc.
I tried to look into the code, but did not want to break anything, 'cos almost everything's going so smoothly now.

Though it's not that much of a problem.

[apricotorange]

If you want to manage the rollback and rollforward keys yourself, you can set "config.readback_full" (one of the custom config variables at the beginning of the script) to False, and the script won't touch them. You can then trigger the readback yourself with the action (SetVariable("readback_yvalue", 1.0), ShowMenu("text_history")); maybe put it on a screen which you show at the start of the game, then hide at certain key points.

On a side note, Ren'Py 6.14 will come with some more flexible options for controlling rollback, which might be an alternative to this script depending on your use-case.