File content as of revision 1:34e76c0cbe5a:

#include "debounce_button.h"

/**
    TODO
    ----
    -   A debouncer has to be present: the built-in buttons of the Nucleo aren't that good, so false positives have to be filtered out. 
        Find a method such that false calls of this function are going to be filtered out. 
        The main loop also needs to know when it can process the further instructions.
        An acceptable time to disable further false positives is between 50ms and 100ms.
    -   The user needs to be able to click the button multiple times in 1 second. 
        The main loop needs to know how many times the user has pressed the button, such that
        it can link different procedures to the different multiclicks. The main loop also needs
        to know when this function is counting the clicks. Therefore, it has to wait until the clicks have been counted
        before it can proceed.
    -   LED1 needs to be turned on while the function is counting the amount of clicks within 1 second.
    
    Some tips and tricks:
    -   To use the built-in LED:
            DigitalOut led1(LED1);
            ...
            led1 = 1;
    -   To delay the call of a function:
            Timeout someTimeout;
            ...
            someTimeout.attach(callback(&anotherFunction), 0.5) with 0.5 as 500 milliseconds
    -   The variables that are used in interrupt callbacks have to be volatile, 
        because these variables can change at any time. Therefore, the compiler is not 
        going to make optimisations.
    -   Use boolean flags to send information between different processes.
    -   In the header file are extra functions and variables that can help you developing these procedures.
        You can add, change or remove these functions and variables at any time, as long as it is clear what you've done.
*/

/**
    This function is called when the button has been pressed by the user.
*/

void button1_onpressed_cb(void)
{
    
}