This lets you make buttons feel like part of the rest of your UI instead of defaulting to one shared look everywhere.
What You Can Style
For each Button, you can assign:
FontDefault ImageHover ImagePressed ImageDisabled Image
You can also use the colour fields to reinforce each state visually.
Step 1: Assign a Button Font
Select the Button in the hierarchy and open the Button card in the Inspector.
From there, you can:
- pick a font from the popup
- drag a font asset onto the field
- clear the field to use the default bundled font
This is useful when:
- a menu button needs a display font
- a title screen needs a more expressive type style
- a HUD button needs tighter visual alignment with the rest of your art direction
Step 2: Assign State Images
Use the image fields in the same Button card:
Default Imagefor the idle stateHover Imagewhile the pointer is over the buttonPressed Imagewhile the button is being pressedDisabled Imagewhen the button is not interactable
Start by assigning the default image first. Then add the other state images where you want the visual to change.
Step 3: Use Colour as Support
If a state image is empty, Lenga falls back to the default image and the state colour.
If no image is assigned at all, the button is drawn with its colour fields.
That means colours still matter even when you are working with image-driven buttons.
A Good Workflow
For most menus:
- assign the default image
- assign the font
- add hover and pressed images
- tune the colours for state feedback
That gives you a stable base before you start polishing.