We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The documentation is fantastic, the best I've ever seen.
On this page there is documentation on how to enable interupts
https://easybtn.earias.me/docs/fundamentals
Yet its not clear what INTERUPT should be.
INTERUPT
Should INTERUPT be the pin on the arduino? ❌
void buttonISR() { button.read(2); }
Should INTERUPT be the Interupt name on the arduino? ❌
void buttonISR() { button.read(INT.1); }
https://www.arduino.cc/reference/en/language/functions/external-interrupts/attachinterrupt/
Should INTERUPT be the string litteral 'INTERUPT' ? ❌
void buttonISR() { button.read(INTERUPT); }
src/main.cpp:91:15: error: 'INTERUPT' was not declared in this scope
Sorry if this is a beginner question. If I'm running into this obstacle, most likely someone else is too.
The text was updated successfully, but these errors were encountered:
Looking at the interrupt example in the examples folder shows that no interupt is provided to button.read().
button.read()
https://github.com/evert-arias/EasyButton/blob/main/examples/Interrupts/Interrupts.ino#L31
Sorry, something went wrong.
No branches or pull requests
The documentation is fantastic, the best I've ever seen.
On this page there is documentation on how to enable interupts
https://easybtn.earias.me/docs/fundamentals
Yet its not clear what
INTERUPT
should be.Should INTERUPT be the pin on the arduino? ❌
Should INTERUPT be the Interupt name on the arduino? ❌
https://www.arduino.cc/reference/en/language/functions/external-interrupts/attachinterrupt/
Should INTERUPT be the string litteral 'INTERUPT' ? ❌
Sorry if this is a beginner question. If I'm running into this obstacle, most likely someone else is too.
The text was updated successfully, but these errors were encountered: