Closed jamesmyatt closed 4 years ago
This is just an oversight. I will look into this when I come back from vacation. I want to split the debouncing code from the hardware layer at the same time.
@jamesmyatt Those methods are private because they might change in the future. They are linked to space saving and not to the functioning of the algorithm. Anyways, I merged a lot of changes.
Why are the following methods all private:
when the attribute that they concern is protected?
I'm not sure it makes sense to be more restrictive of the methods than the underlying attribute.