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
Describe the bug
As per the title, if you attempt to pulse a PWMLED via callback associated with a button press, the LED doesn't actually start pulsing until after the function returns. I'd assume this is something to do with how callbacks are handled within the library, as the function works as expected if you call it directly. blink() displays similar behaviour, in that the LED is initially illuminated when the function is called but doesn't actually start blinking until after the function returns.
To Reproduce
Run the following code (obviously GPIO pins need to be changed as appropriate) and press your button.
Describe the bug
As per the title, if you attempt to pulse a PWMLED via callback associated with a button press, the LED doesn't actually start pulsing until after the function returns. I'd assume this is something to do with how callbacks are handled within the library, as the function works as expected if you call it directly.
blink()
displays similar behaviour, in that the LED is initially illuminated when the function is called but doesn't actually start blinking until after the function returns.To Reproduce
Run the following code (obviously GPIO pins need to be changed as appropriate) and press your button.
Expected behaviour
I'd expect the LED to start pulsing as soon as the first statement is printed and before the function returns.
System information:
The text was updated successfully, but these errors were encountered: