[SOLVED] Problem with Textbutton Hover

[redeller]

Hi I'm having trouble with textbutton styling. So far, this is my code:

Code: Select all

style fight_button:
    color "#3f1414" 
    size 100
    pos(300,100) 
    font "../fonts/arcade_n.ttf"
    hover_color "#926464" 

style flight_button:
    color "#3f1414" 
    size 100
    pos(1050,100) 
    font "../fonts/arcade_n.ttf"
    hover_color "#926464"

for both of the textbuttons (they are basically the same except for position). Here is how I call them:

Code: Select all

textbutton "FIGHT" text_style "fight_button" action [SetVariable("fight", True)] at my_shake, fade_in2
textbutton "FLIGHT" text_style "flight_button" action [SetVariable("flight", True)] at my_shake, fade_in3
        

They both show up fine, but the problem occurs when I hover over the button, it doesn't select the proper area. At the pos specified, the textbutton is not selected. But when I hover my mouse at the top left of the screen, the "FLIGHT" button is selected. I tried playing around with the pos, action, and text but it remains the same. The button is not recognized in the correct area.

What am I doing wrong?

Thanks in advance!

[Imperf3kt]

Are you using the textbuttons as part of a screen, or directly in your script?
For example, this is incorrect, don't use screen language like this:

Code: Select all

label start:
    "Textbuttons are screen language, this is not a screen."
    "This example is incorrect."
    textbutton "myButton" action NullAction()
    return

The correct way to use a textbutton:

Code: Select all

## Place this somewhere in screens.rpy, or outside any label.
screen fight():
    vbox:
        textbutton "myButton" action NullAction()
        
## The rest goes in script.rpy
label start:
    "This is one of many correct ways to show a textbutton."
    show screen fight
    "the button should now show"
    return

There are many more ways top show the button and control how it behaves, all depends what exactly you want to achieve, for example, you may want to call the screen instead or might want to call the screen with keyword arguments so the position of the button can be changed dynamically etc.