Clearing a screen after ui.interact()

[marigoldsofthenight]

I have a section of my novel where the user must press the right button on a keypad. I have made the keypad as a separate screen, everything is working well, but I want to get rid of it after the button has been pressed. Here's the code thus far in the main script:

Code: Select all

label keypadtest:    
    o "I'm going to show you a keypad. Please press 7." 
    show screen keypad
    $renpy.pause()
    
    while True: 
        $ result = ui.interact()
    

I use ui.interact() to keep the keypad screen up there (it's a screen full of text buttons that emulates the numbers on a phone). What command do I use to tell repy to close that screen after a particular button has been pressed?

[xela]

I have a section of my novel where the user must press the right button on a keypad. I have made the keypad as a separate screen, everything is working well, but I want to get rid of it after the button has been pressed. Here's the code thus far in the main script:

Code: Select all

label keypadtest:    
    o "I'm going to show you a keypad. Please press 7." 
    show screen keypad
    $renpy.pause()
    
    while True: 
        $ result = ui.interact()
    

I use ui.interact() to keep the keypad screen up there (it's a screen full of text buttons that emulates the numbers on a phone). What command do I use to tell repy to close that screen after a particular button has been pressed?

This is not something you use a while loop for, especially not with one key... either call the keypad or have 7 return some you can intercept (like a string/integer or string inside of a list/tuple) and hide the screen/terminate the loop at that return. I would have honestly used call screen here, while loop is redundant unless it needs to handle huge amounts of logic like in Battle Engines/Complex Inventories/Complex profile screens etc.

[marigoldsofthenight]

This is not something you use a while loop for, especially not with one key... either call the keypad or have 7 return some you can intercept (like a string/integer or string inside of a list/tuple) and hide the screen/terminate the loop at that return. I would have honestly used call screen here, while loop is redundant unless it needs to handle huge amounts of logic like in Battle Engines/Complex Inventories/Complex profile screens etc.

Much obliged! Still learning how all of these screens and whatnot work. Thank you for pointing me in the right direction. Problem solved now!