button action different on Android
Sannyasin Brahmanathaswami
brahma at hindu.org
Wed May 30 21:18:10 EDT 2018
I'm seeing similar behavior on the main navigation buttons at bottom of the screen. In SivaSiva app Although it behaves differently, I suspect similar underlying engine issue
I have large fingers, Example, the "Home" (a button that takes you back) icon has plenty of touch space. It is on left bottom..
When I touch it carefully, and slowly with my thumb or big forefinger, and release, it seems not to send mouseup. I was wracking head around this... but when I tried to touched very lightly, using my "little pinky" .. it was immediately responsive!
I had a round of support questions to business support on the subjects
All they could come up with was. "I think it might just be that it is a smallish area that is quite hard to hit. You could increase the height of the SVG widgets to be as tall as the bar or perhaps providing some visual feedback to the user."
But that is not it. The finger is touch the button. I was told
"To try and see what is happening with the buttons and detect when they are
actually being hit you could add some logging to the mouseUp handler."
and, "a slow, full finger push" on the button indeed gives no mouseup... but a light touch will!
Are all of your button SVG Widgets? I gave up on this, it was so mysterious.
After 1.2 goes out the week, I will test it again
BR
Nicolas Cueto via use-livecode
Wrote:
On Android, after a button is tapped, its appearance is inconsistent. It
looks either:
1. first depressed (inset?) and then un-depressed
2. first depressed and remains depressed
It seems the difference in appearance depends on the time length of the
tap, and perhaps too on how narrow/small the buttons are (my fingertip is
almost larger than the button height). If a tap is very brief, the button
returns to an un-depressed state; if longishly held, the button stays
depressed.
More information about the use-livecode
mailing list