Button._start_active_affect does not respect App.animation_level

[dillydill123]

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

[github-actions[bot]]

We found the following entry in the FAQ which you may find helpful:

• No widget called TextLog

Feel free to close this issue if you found an answer in the FAQ. Otherwise, please give us a little time to review.

This is an automated reply, generated by FAQtory

[willmcgugan]

By using Pilot.click you are simulating a user. And if a user clicks rapidly on a button it will only register a single press. This is a good thing because it prevents the user from actioning a button more than once, before the app can respond.

If you aren't interesting in simulating a user, you could do something like the following:

await pilot.app.query(MyButton).press()