Re: What to do with long press? (was Re: Set DoubleClickInterval very low!)

Roger Eller wrote: > On Thu, Aug 4, 2016 at 12:46 PM, Richard Gaskin wrote: >> And is there a way to make mobile-savvy menus from LC popup menus, >> or do we need to roll our own for those too? > > I remember an old webinar where LC demonstrated (at least on iOS) a > desktop pop-up automatically

Re: Set DoubleClickInterval very low!

On 8/4/2016 12:37 PM, Sannyasin Brahmanathaswami wrote: Jacqueline: can you supply a small "long press" trap snippet for us here? tks I see Richard beat me to it, which was nice. Jacqueline: how do you give a mobile user on android the ability to select a range of text versus just a word?

Re: Set DoubleClickInterval very low!

Sannyasin Brahmanathaswami wrote: It's very simple: on mouseup # do something right now and don't wait more than 100 milliseconds # because we don't use double clicks anywhere in this app end mouseup There is no "dual model" to even think about. If you have no interest in

Re: What to do with long press? (was Re: Set DoubleClickInterval very low!)

I remember an old webinar where LC demonstrated (at least on iOS) a desktop pop-up automatically "just worked" as a mobile pick list. I believe it was Ben Beaumont showing that. I never saw it for Android, but that was no surprise. ~Roger On Thu, Aug 4, 2016 at 12:46 PM, Richard Gaskin

Re: What to do with long press? (was Re: Set DoubleClickInterval very low!)

Well, if I said "only" I shouldn't have. It's used to select text, and a long press on an embedded link usually shows the full URL along with a list of options on what to do with the link (copy, open, save to disk, etc. ) Long pressing a word in my ebook reader puts up a mini menu above the

Re: Set DoubleClickInterval very low!

On August 4, 2016 11:11:22 AM Richard Gaskin wrote: , you might consider removing that dual model altogether and finding a different means of delivering the options you're seeking to provide for the user. Just a personal anecdote: I've spent most of my mobile time

What to do with long press? (was Re: Set DoubleClickInterval very low!)

J. Landman Gay wrote: > Note that on Android double clicks are almost unheard of. Android > uses a long press for alternative actions. ...as long as that alternate action is a tooltip ("toast"). :) I was thinking about long press recently with an app I'm making, and it reminded me of our

Re: Set DoubleClickInterval very low!

Note that on Android double clicks are almost unheard of. Android uses a long press for alternative actions. On August 4, 2016 10:31:01 AM Sannyasin Brahmanathaswami wrote: @ Mark which confirms that lowering the doubleClick Interval to thereby increase responsiveness

Re: Set DoubleClickInterval very low!

Sannyasin Brahmanathaswami wrote: > On 8/3/16, 9:02 PM, Mark Waddingham wrote: > >> In order for you to be able to do completely different things on >> click and double click you need to wait and see if a double click >> occurs before the doubleClickInterval and if it does not *then* do >> the

Re: Set DoubleClickInterval very low!

@ Mark which confirms that lowering the doubleClick Interval to thereby increase responsiveness of a single click is not a bug, but, just the way it works… On 8/3/16, 9:02 PM, "use-livecode on behalf of Mark Waddingham"

Re: Set DoubleClickInterval very low!

A moment ago I wrote: > Unless you have some other factor at play there, changing the value > of any property not related to an action should never be needed, and > should be considered a bug. The first clause is key there. I haven't spent much time with iOS yet, and perhaps there's a bug in

Re: Set DoubleClickInterval very low!

Sannyasin Brahmanathaswami wrote: > Suffice it to say that > > set the doubleClickInterval to 100 > > Immediately turned our new app into a "snappy responsive" animal. > > Which is good, because the prevailing thought was beginning to become > "Livecode is really to slow for mobile." when in

Re: Set DoubleClickInterval very low!

Peter M. Brigham wrote: > So I must not be understanding this. If you want something to happen > on mouseup and something else to happen on mousedoubleup, then how > do you do it? The other question is *why* would you do it? A control usually has an interaction semantics role of either a verb

Re: Set DoubleClickInterval very low!

That's what I thought. The engine is certainly not clairvoyant. I can script around this. I was hoping that the newer LC versions had somehow made it easier to do different things with single and double clicks, since I'm not sure why you would ever want a doubleclick to default to including the

Re: Set DoubleClickInterval very low!

All I was pointing out was that the current mechanism means you need to put in shim doubleMouse handlers in the controls which don't respond to double clicks *and* you have to write more code if you want to handle triple click. A simpler pattern (I think at least) is the one I suggested where

Re: Set DoubleClickInterval very low!

In order for you to be able to do completely different things on click and double click you need to wait and see if a double click occurs before the doubleClickInterval and if it does not *then* do the single click action. After all, the engine is not clairvoyant. This is why click then double

Re: Set DoubleClickInterval very low!

@ Mark Thank you for the explanation. I would have to study this out more to reply with anything more intelligent. Suffice it to say that set the doubleClickInterval to 100 Immediately turned our new app into a "snappy responsive" animal. Which is good, because the prevailing thought was

Re: Set DoubleClickInterval very low!

So I must not be understanding this. If you want something to happen on mouseup and something else to happen on mousedoubleup, then how do you do it? If I put this into a button script: on mousedown put "mousedown" & cr after fld "text" end mousedown on mouseUp put "mouseup" & cr after

Touch everywhere (was Re: Set DoubleClickInterval very low!)

Earlier I wrote in reply to Mark Waddingham: > I think LC's implementation is similar to how most OSes handle it, > at least judging from the old Inside Mac details on click interval > and slop rect, and the XP refs I used to read. > > Given that, I'm not sure we need to have you spend time away

Re: Set DoubleClickInterval very low!

Mark Waddingham wrote: > On 2016-08-04 01:32, Sannyasin Brahmanathaswami wrote: >> How is it a bug? logically the engine must wait for the double click >> interval before responding or double clicks could never be passed? >> N'est ce pas? > > No - that isn't how double clicks work in LiveCode.

Re: Set DoubleClickInterval very low!

On 2016-08-04 01:32, Sannyasin Brahmanathaswami wrote: How is it a bug? logically the engine must wait for the double click interval before responding or double clicks could never be passed? N'est ce pas? No - that isn't how double clicks work in LiveCode. On the first mouseDown the engine:

Re: Set DoubleClickInterval very low!

How is it a bug? logically the engine must wait for the double click interval before responding or double clicks could never be passed? N'est ce pas? BR : Richard Gaskin wrote: With any single-click gesture there is of course no interval, so any effect you may see with changing the

Re: Set DoubleClickInterval very low!

Sannyasin Brahmanathaswami wrote: > For Mobile newbies > > Is your Mobile App Slow to Respond to Taps? > > the default doubleclickinterval for LC is 800 milliseconds. This is > nearly 1 whole second the engine waits before doing anything with > your click/tap. > > This carries over to your

Set DoubleClickInterval very low!

For Mobile newbies Is your Mobile App Slow to Respond to Taps? the default doubleclickinterval for LC is 800 milliseconds. This is nearly 1 whole second the engine waits before doing anything with your click/tap. This carries over to your mobile app. No wonder the app feels sluggish and