You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think if App.animation_level is set to "none" it should not run any active effect on the button. My use case is that for tests, if my pilot tries to click the same button twice in a row, it happens so fast that the -active class is still set for the button and the click is consumed without self.press() being called.
My current work around is to patch this function. mock.patch("textual.widgets._button.Button._start_active_affect")
Also nit but I think it should be start_active_effect and not start_active_affect
The text was updated successfully, but these errors were encountered:
dillydill123
changed the title
Button._start_active_effect does not respect App.animation_levelButton._start_active_affect does not respect App.animation_levelSep 26, 2024
I think if
App.animation_level
is set to"none"
it should not run any active effect on the button. My use case is that for tests, if my pilot tries to click the same button twice in a row, it happens so fast that the-active
class is still set for the button and the click is consumed withoutself.press()
being called.My current work around is to patch this function.
mock.patch("textual.widgets._button.Button._start_active_affect")
Also nit but I think it should be start_active_effect and not start_active_affect
The text was updated successfully, but these errors were encountered: