Here's an example imagemap main menu:
Code: Select all
screen main_menu: imagemap "main_menu_*.jpg" hotspot (100, 100, 200, 40) clicked Start() if persistent.unlocked_extras: hotspot (100, 140, 200, 40) clicked Start("extras") else: hotspot (100, 140, 200, 40) clicked Start("extras_locked") hotspot (100, 180, 200, 40) clicked JumpScreen("load_screen") hotspot (100, 220, 200, 40) clicked JumpScreen("preferences_screen") hotspot (100, 260, 200, 40) clicked Quit()
- A start button.
- A button that goes to the extras, if they've been unlocked, else goes to the extras_locked screen.
- A button that goes to the load screen.
- A button that goes to the preferences screen.
- A button that quits the game.
In this example, I've given the hotspots as (x, y, w, h) - that is, we give the upper-left coordinate, and then the width and height. Currently, for imagemaps, we give hotspots as (x1, y1, x2, y2) - the coordinates of the upper-left and lower-right corners of the hotspot.
I'd like to change how we specify imagemaps, for consistency with the rest of Ren'Py. Apart from imagemaps, we use (x, y, w, h) everywhere else in Ren'Py, like for cropping. But at the same time, I'd like for this not to make the new scheme useless.
So, my question to people who currently make or are considering making imagemap menus is this: How would this new scheme affect your workflow? Regularity is nice, but I don't want to make designing menus impractically difficult.