Groups > comp.lang.java.programmer > #3646

Touch Debouncing

Path	csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!203.109.252.33.MISMATCH!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail
From	Lawrence D'Oliveiro <ldo@geek-central.gen.new_zealand>
Newsgroups	comp.lang.java.programmer
Subject	Touch Debouncing
Followup-To	comp.lang.java.programmer
Date	Fri, 06 May 2011 18:46:05 +1200
Organization	Geek Central
Lines	8
Message-ID	<iq05fd$jpv$5@lust.ihug.co.nz> (permalink)
NNTP-Posting-Host	118-92-95-178.dsl.dyn.ihug.co.nz
Mime-Version	1.0
Content-Type	text/plain; charset="UTF-8"
Content-Transfer-Encoding	8Bit
X-Trace	lust.ihug.co.nz 1304664365 20287 118.92.95.178 (6 May 2011 06:46:05 GMT)
X-Complaints-To	abuse@ihug.co.nz
NNTP-Posting-Date	Fri, 6 May 2011 06:46:05 +0000 (UTC)
User-Agent	KNode/4.4.7
Xref	x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:3646

Followups directed to: comp.lang.java.programmer

Show key headers only | View raw

I have an Android app where the buttons respond immediately the user touches 
them, rather than when they release the touch. (Why? Because that’s how the 
original device that I’m emulating worked.)

Every now and then I’d touch a button once, and have it trigger twice. 
Finally I had to put in a debounce: any touch-down notification I get that’s 
less than 0.1 second after the previous one is ignored. That cured the 
problem.

Back to comp.lang.java.programmer | Previous | Next | Find similar

Thread

Touch Debouncing Lawrence D'Oliveiro <ldo@geek-central.gen.new_zealand> - 2011-05-06 18:46 +1200

csiph-web