Hi,
Q1: Is post(action) equivalent to postDelayed(action, 0)?
Q2: If a view implements a never stopping cycle like this, depending
on two time parameters, N and T:
public void timerEvent() {
final class Timer implements Runnable {
public void run() {
timerEvent();
}
}
native_code(); // guaranteed to run no
longer than N msecs
postDelayed(new Timer(), T);
}
what combinations of N and T ranges (including T = 0) are acceptable
to make sure the view remains responsive to touch and other user-
generated events, and "force close/wait" dialog does not appear?
I currently set N to 200msec max. Any lower bound on T?
In other words, if T = 0 and a touch event arrived while in native
code, will it be processed by the view at all, or is it necessary to
have T > 0 to guarantee that touch event will be processed?
Thanks.
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
