[Solved]Yes/No Prompt Customization

[mjshi]

Two questions about the yes/no prompt's customization--

1) Is it possible to add a gutter/buffer for the _message?
I'm getting something like-

which, frankly, doesn't look nice.

2) Is it possible to add a black background to the "Are you sure that you want to quit?" screen, but only when the screen doesn't appear on top of any other screens/layer over them?
Honestly, looking at a checkerboard of grey squares--

isn't very interesting either.

Thanks in advance!

[SundownKid]

First - yes, you will have to make the text have an xmaximum.

Second - that is not necessary. There is a way to make the yes/no prompt not have to erase the menu, as long as you remove "tag menu" (meaning it goes on top of the menu instead of replacing it) and add "modal True" (meaning you cannot press underlying buttons while it's active) it should work.

[mjshi]

First- thank you!

Second- Yes, this is the code I have, but whenever you click the windows x button it still replaces the currently occurring things--

Code: Select all

screen yesno_prompt(message, yes_action, no_action):

  modal True
  
  imagemap:
    xalign 0.5
    yalign 0.45
    auto "yesno_%s.png"
      
    hotspot (98, 145, 58, 36) action yes_action
    hotspot (277, 143, 51, 32) action no_action
    
  label _(message):
    text_style "yesno_label_text"
    xalign 0.5
    yalign 0.45
    # I'll add an xmaximum after dealing with the second problem.

init -2 python:    
  style.yesno_button.size_group = "yesno"
  style.yesno_label_text.text_align = 0.5
  style.yesno_label_text.color = "#000"

and I'll attach the images--

Cases where the yes/no replaces whatever is below it--
- pressing the x button on the main menu
- pressing the x button ingame
- pressing the x button in any of the navigation's menus (save, load, prefs)

Cases where the yes/no doesn't replace whatever is below it--
- overwriting a save
- loading a save
- returning to the main menu
- clicking the quit button in game navigation-
- clicking the quit button in the main menu (when confirm is not set to false)

[xela]

Code: Select all

init python:
    config.quit_action = Quit()

Fixes the second issue.

[mjshi]

I have no idea what you just did, but thank you xD

--Marked as solved.

[nyaatrap]

Code: Select all

init python:
    config.quit_action = Quit()

Fixes the second issue.

I wonder why this isn't ren'py default behavior. Is there any side-effect, or just for compatibility reason?

[xela]

Only PyTom can tell... due to compatibility reasons, quitting logic is an intertwined mess of labels, functions and wrappers or at least it's what it looks like to me. I joined the Ren'Py world after SL was introduced so I have no idea how ui interface behaved in these cases in the past.

I do not however believe that there can be a sideeffect to this when used in modern Ren'Py as it still saves the game if setup to do so and quits the game. It's not like we require this class to do anything else

[Donmai]

Honestly, looking at a checkerboard of grey squares--

I see many people disliking the 'grey squares', for some reason. Maybe because few of them seem to notice that the checkerboard background is only visible while

Code: Select all

config.developer = True

If you make it False, then the checkerboard is gone and the background will be a solid color when you run the game.