It is by design and the intention is that you can interrupt the thread if you want to cancel. Typically, you would use a TimerTask for that purpose.
On Sun, Mar 6, 2016 at 8:54 PM, Kevin Miller <[email protected]> wrote: > Hello, > I'm using an HC-SR04 in a IOIOService loop. I used a Timer to set a flag > periodically so that the Looper will know when it should perform a ranging. > > If I use getDurationSync() the Looper will hang on getDurationSync after > about 10 readings with the timer set to 500 (ms?) delay between triggers. > > Second, if the sensor is unplugged, it hangs at getDuration() in every > case no matter what form of getDuration I use or what the timer delay is. > Is this by design to hang if there is no pulse, or is it possible to > timeout? > > Thanks, > Kevin > > -- > You received this message because you are subscribed to the Google Groups > "ioio-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/ioio-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
