[SOLVED] "Unbound method get_tooltip() must be called with Return"

[Kinmoku]

Hi all,

I'm revisiting an older project and whenever I hover over the text button in a screen, I get an error:

Code: Select all

I'm sorry, but an uncaught exception occurred.

While running game code:
  File "game/script.rpy", line 6022, in script call
    call first_memory
  File "game/memories.rpy", line 398, in script
    call screen help_katie
  File "renpy/common/000statements.rpy", line 531, in execute_call_screen
    store._return = renpy.call_screen(name, *args, **kwargs)
TypeError: unbound method get_tooltip() must be called with Return instance as first argument (got nothing instead)

-- Full Traceback ------------------------------------------------------------

Full traceback:
  File "game/script.rpy", line 6022, in script call
    call first_memory
  File "game/memories.rpy", line 398, in script
    call screen help_katie
  File "/Applications/renpy-6.99.11-sdk/renpy/ast.py", line 1947, in execute
    self.call("execute")
  File "/Applications/renpy-6.99.11-sdk/renpy/ast.py", line 1935, in call
    return renpy.statements.call(method, parsed, *args, **kwargs)
  File "/Applications/renpy-6.99.11-sdk/renpy/statements.py", line 277, in call
    return method(parsed, *args, **kwargs)
  File "renpy/common/000statements.rpy", line 531, in execute_call_screen
    store._return = renpy.call_screen(name, *args, **kwargs)
  File "/Applications/renpy-6.99.11-sdk/renpy/exports.py", line 2896, in call_screen
    rv = renpy.ui.interact(mouse="screen", type="screen", roll_forward=roll_forward)
  File "/Applications/renpy-6.99.11-sdk/renpy/ui.py", line 295, in interact
    rv = renpy.game.interface.interact(roll_forward=roll_forward, **kwargs)
  File "/Applications/renpy-6.99.11-sdk/renpy/display/core.py", line 2701, in interact
    repeat, rv = self.interact_core(preloads=preloads, trans_pause=trans_pause, **kwargs)
  File "/Applications/renpy-6.99.11-sdk/renpy/display/core.py", line 3509, in interact_core
    rv = renpy.display.focus.mouse_handler(ev, x, y)
  File "/Applications/renpy-6.99.11-sdk/renpy/display/focus.py", line 397, in mouse_handler
    return change_focus(new_focus, default=default)
  File "/Applications/renpy-6.99.11-sdk/renpy/display/focus.py", line 352, in change_focus
    set_focused(current, newfocus.arg, newfocus.screen)
  File "/Applications/renpy-6.99.11-sdk/renpy/display/focus.py", line 109, in set_focused
    new_tooltip = widget._get_tooltip()
  File "/Applications/renpy-6.99.11-sdk/renpy/display/behavior.py", line 746, in _get_tooltip
    return get_tooltip(self.action)
  File "/Applications/renpy-6.99.11-sdk/renpy/display/behavior.py", line 373, in get_tooltip
    return func()
TypeError: unbound method get_tooltip() must be called with Return instance as first argument (got nothing instead)

It's always worked before as it's a pretty simple screen:

Code: Select all

screen help_katie:
    hbox:
        xpos 650
        ypos 400 
        
        textbutton "HELP HER" action Return

I've made some changes since I last tested this part, but mainly narrative. Otherwise, all I have done is update Ren'Py. Any ideas? I can't find this issue online.

[Remix]

action Return()

[Kinmoku]

action Return()

It works thank you. What is the reason for it to stop working now?

[drKlauz]

Return is class, calling class, like this - Return(), is instancing this class, it return instance of class. Basically class is blueprint, instance of class is actual thing made by this blueprint.
Instance of Return return either None or some value.
But Return() also return value - instance of class.
So sometimes using action Return will work, even if it is obvious bug.
Unless you really know what you doing, like using class method __call__ etc, you should always use action ActionName(action_arguments), not action ActionName.

[Kinmoku]

Return is class, calling class, like this - Return(), is instancing this class, it return instance of class. Basically class is blueprint, instance of class is actual thing made by this blueprint.
Instance of Return return either None or some value.
But Return() also return value - instance of class.
So sometimes using action Return will work, even if it is obvious bug.
Unless you really know what you doing, like using class method __call__ etc, you should always use action ActionName(action_arguments), not action ActionName.

Okay Thank you for explaining it to me.

[philat]

Updates often enforce correct syntax when mistakes were allowed before.