Returning from Ren'py call stack to Python call stack.

[FortOyer]

I have my program set up with quite a few function callbacks, these functions can be expected to use renpy.call, and then continue where they left off. Unfortunately the renpy.call kills the python function before it'd complete gracefully.

Calling in a new context would work, but the new context wouldn't save any dialogue in the call statement to rollback.

Here's a general example where setting t to "Last Call" never happens.

Code: Select all

define e = Character('Eileen', color="#c8ffc8")

init:
    define t = "Initial Value"

init python:
        def func():
            store.t = "Second Pass"
            
        def func2():
            renpy.call("stack_test")
            store.t = "Last Call"
 
label stack_test:
    $ t = "Penultimate Call"
    e "[t]"
    return 
    
# The game starts here.
label start:
    e "[t]"
    $ func()
    e "[t]"
    $ func2()
    e "[t]"    
    return

Is there a workaround for this?

[Milkymalk]

I had the same problem. Unfortunately, renpy.call() always aborts the Python stack and returns to the Ren'py script. You should try to avoid using renpy.call(), which means only executing functions when you are sure you don't need to call a label inbetween.

Fortunately, you can call labels with arguments and then include a Python block if necessary to "imitate" Python functions:

Code: Select all

label callme(a):
    ..stuff..
    python:
        ..stuff..

[FortOyer]

Damn and damn! Ah well, will redesign with that in mind, thank-you!

[xela]

Milkymalk is right, there is nothing you can do here... but there is always a workaround (in this case a workaround will prolly result in better code).