Bodmer

The button class is a bit too basic at the moment so extra functionality would be of benefit and simplify sketches. My initial thoughts need more consideration but are: 1....

Have thought a bit more about this. It would be simpler to have one action callback as you suggest, then within that callback a user can call getState and decide...

I have thought further on this and concluded that an independant buttons support library is the way to go. This then reduces the maintenance, development and bug/question/documentation support load on...

I have created a draft library here: https://github.com/Bodmer/TFT_eButton It is working but has a few rough edges. The example needs work but demonstrates: - A toggle button - A button...

> * Is there a reason why one of the defined button states isn't `HELD` Nope, just a test example for a momentary, non-latching push button. This is not a...

I will think on this further. I am wondering if a new action is needed. Have you tried the original eBotton example sketch and looked at the serial outputs? The...

Screen buttons share a lot of common action requirements to physical switch buttons, so I have been looking at this library which seems popular: https://github.com/LennartHennigs/Button2 I think screen and physical...

I've got an urgent (paid for) hardware project to do now so I will not be able to spend any time developing the TFT_eButton library further for quite a while....

I have ported a library from Kris Kasprzak that seems to work quite well. Copy here: https://github.com/Bodmer/ILI9341_t3_controls It has a few quirks but it produces some nice looking functional screens....

Writing support documentation has been on my "To Do" list for a long time. It would take many hours to do this and at the moment I am busy with...