# Cancel button code

**URL:** <https://forum.arduino.cc/t/cancel-button-code/1191125>\
**Category:** Programming\
**Created:** [November 19, 2023, 11:37pm UTC](https://forum.arduino.cc/t/cancel-button-code/1191125 "2023-11-19T23:37:12Z")\
**Posts on this page:** 1\
**Showing post:** 39

<div class="post-metadata">

**Author:** ![Grumpy\_Mike](https://dub1.discourse-cdn.com/arduino/user_avatar/forum.arduino.cc/grumpy_mike/32/213521_2.png) [@Grumpy\_Mike](https://forum.arduino.cc/u/Grumpy_Mike)\
**Post date:** [November 21, 2023, 5:57am UTC](https://forum.arduino.cc/t/cancel-button-code/1191125/39 "2023-11-21T05:57:46Z")

</div>

@underhilll  
It seems you do not like / get the conventional way of doing things. I did come up with an alternative technique I called a commutable delay.

This is a tutorial on that method.

> [@Between Delay and State Machine - Commutable Delay](https://forum.arduino.cc/t/between-delay-and-state-machine-commutable-delay/1059712):
>
> An alternative type of delay One common question here that seems to gets asked every day, is about mitigating the blocking effects of the delay function. Once a delay has been called the Arduino can do nothing until this delay has been finished. This is often called blocking code and getting round this can be quite baffling for a beginner. Often a beginner here is pointed to the blink without delay example code in the IDE. The problem is that this sort of pseudo multitasking is often a large s…

---

_[View the full topic](https://forum.arduino.cc/t/cancel-button-code/1191125)._
