Hi Swami,
How about using the mousestlilldown command and call the mouseup within
that?
Lagi
On 31 May 2018 at 14:56, Sannyasin Brahmanathaswami via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Well, "rather Android ceding time for that sort of thing."
>
> While it may not be a LC
Well, "rather Android ceding time for that sort of thing."
While it may not be a LC "problem" ... we need a way to avoid the long press
behavior (if that is it is?) and ensure the button responds. N'est ce pas?
BR
On 5/30/18, 7:15 PM, "use-livecode on behalf of J. Landman Gay via
use-liveco
There is a convention on Android where a long press on a button can, and
often does, show a tooltip or a label. This is handy when you don't know
what an icon means. Long presses on Android can also behave like right
clicks on desktop to provide alternate behaviors. It may be that the
problem i
Is it possible that a long press is sending a different message (and not the
mouseUp)? I do not have Android development set up yet (or a device other than
a Fire) so I can’t test to see.
On May 30, 2018, 8:18 PM -0500, Sannyasin Brahmanathaswami via use-livecode
, wrote:
> I'm seeing similar be
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
If you mean you don't want any visible reaction at all, turn off
autohilite, sharedhilite, focuswithkeyboard, focus border, and defaultbutton.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 29, 2018 8:37:09 PM Nicolas Cueto via us
Developing a stack on windows, which has two groups of 30 buttons
contiguosly placed, and each button's settings are:
'''
style=standard
autohilite, sharedhilite, focuswithkeyboard, focusborder,
defaultbutton,disa
