Adding triple tap to select current row for widget.Entry

[dweymouth]

Description:

Fixes #4328

Checklist:

• Tests included.
• Lint and formatter run with no errors.
• Tests all pass.

Where applicable:

[coveralls]

coverage: 64.614% (-0.5%) from 65.084%
when pulling f710676 on dweymouth:entry-triple-tap
into 2921c11 on fyne-io:develop.

[andydotxyz]

Great to have this addition - but I wonder if we can avoid duplicating constants?

[dweymouth]

Looks like there's still an import cycle in test code. I'll take a look in a bit

[Jacalz]

This is wonderful. What a difference in usability! Thanks :D
Just left one comment on the placement of the consts :)

[Jacalz]

I wonder, should we expose an interface for making a widget triple tappable instead of exposing the double tap delay?

[dweymouth]

We figured that Entry was probably the only widget that needed triple tap. Also personally I'd like the double tap delay to be exposed since I have my list rows in Supersonic implement their own double tap logic (here - so that tap can instantly trigger to select the row of a tracklist while double tap can play a track). Having a widget have both Tappable and DoubleTappable means, by design, it won't get the tap event until after the delay, which is not what I wanted in my case.

Edit: either that - or a way to request for a specific widget that the Tapped callback should be invoked immediately even if it may become a DoubleTap if tapped again

[andydotxyz]

Edit: either that - or a way to request for a specific widget that the Tapped callback should be invoked immediately even if it may become a DoubleTap if tapped again

This is tough to be convinced of - as Tapped is an abstract request for the tap event, as you know we have lower level events for when the widget wants to do smarter things. Double tapping, and indeed Triple, are not things that most widgets will be doing (I hope!) as there is no discoverability to these actions.

[andydotxyz]

Thanks, this looks to be in a good place now :)

no longer relevant