Instead implement your own thread.kill() machanism, using existing API provided by the SDK. Manage your thread creation within a threadpool, and use Future.cancel() to kill the running thread:
ThreadPoolExecutor threadPoolExecutor = Executors.newSingleThreadExecutor(); Runnable longRunningTask = new Runnable();
// submit task to threadpool: Future longRunningTaskFurure = threadPoolExecutor.submit(longRunningTask);
... ... // At some point in the future, if you want to kill the task: longRunningTaskFuture.cancel(true); ... ...
Cancel method will behaviour differently based on your task running state, check the API for more details.
I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?
Instead implement your own thread.kill() machanism, using existing API provided by the SDK. Manage your thread creation within a threadpool, and use Future.cancel() to kill the running thread:
ReplyDeleteThreadPoolExecutor threadPoolExecutor = Executors.newSingleThreadExecutor();
Runnable longRunningTask = new Runnable();
// submit task to threadpool:
Future longRunningTaskFurure = threadPoolExecutor.submit(longRunningTask);
... ...
// At some point in the future, if you want to kill the task:
longRunningTaskFuture.cancel(true);
... ...
Cancel method will behaviour differently based on your task running state, check the API for more details.
changeColor is declared as Runnable, which does not have a kill() method.
ReplyDeleteYou need to create your own interface that extends Runnable and adds a (public) kill() method.