I want to save a file before closing my JavaFX application.

This is how I&#39;m setting up the handler in `Main::start`:

    primaryStage.setOnCloseRequest(event -&gt; {
        System.out.println(&quot;Stage is closing&quot;);
        // Save file
    });



And the controller calling `Stage::close` when a button is pressed:

    @FXML
    public void exitApplication(ActionEvent event) {
        ((Stage)rootPane.getScene().getWindow()).close();
    }

 

If I close the window clicking the red X on the window border (the normal way) then I get the output message &quot;`Stage is closing`&quot;, which is the desired behavior.

However, when calling `Controller::exitApplication` the application closes without invoking the handler (there&#39;s no output).

How can I make the controller use the handler I&#39;ve added to `primaryStage`?


    


JavaFX: Stage close handler

I have an issue with the following error in Android:

&gt; CalledFromWrongThreadException;: Only
&gt; the original thread that created a
&gt; view hierarchy can touch its views

It appears to happen when I try to update a Textview in my Activity, the call to update the TextView is from within my Activity but I still get the above error.

I have it like this:

onCreate()
-sets up the buttons and the text view.

onStateChange() - a listener for notifications about state changes, when this gets notification if changes the TextView to say some different text.

When I get notification of a new text I try to change the TextView as so:

    ((TextView)findViewById(R.id.title)).setText(&quot;Some Text&quot;);

But I get the above Error.

From googling it, it appears I should use a handler to change the TextView or maybe use AsyncTask?

Could anyone explain which one would be better to use and why?

**EDIT: ADDED CODE SNIPPETS:**

---

		 public void onCreate(Bundle savedInstanceState) {
		        super.onCreate(savedInstanceState);
		        
				requestWindowFeature(Window.FEATURE_CUSTOM_TITLE);	

				setContentView(R.layout.my);
		        
				getWindow().setFeatureInt(Window.FEATURE_CUSTOM_TITLE, R.layout.my_title);	

				((TextView)findViewById(R.id.time)).setText(&quot;Hello Text&quot;);

				
				findViewById(R.id.keyboardimage).setOnClickListener(new OnClickListener() {
		            public void onClick(View v) {
		            	
		            	Intent dialIntent = new Intent(Intent.ACTION_DIAL, Uri.parse(&quot;tel:&quot;));
		        		startActivity(dialIntent);
		        		
		                    dispatchKeyEvent(new KeyEvent(KeyEvent.ACTION_DOWN,KeyEvent.FLAG_SOFT_KEYBOARD));
		                    dispatchKeyEvent(new KeyEvent(KeyEvent.ACTION_UP, KeyEvent.KEYCODE_BACK));       
		            }
		    });
				
		 }


---

    //CallBacks from running Service

    private final ICallDialogActivity.Stub iCallDialogActivity = new ICallDialogActivity.Stub(){

    @Override
    public void onStateChanged(int callState)
					throws RemoteException {	
				switch(callState){
				case GlobalData.CALL_STATUS_IDLE:
					 
					break;
					
				case GlobalData.CALL_STATUS_DISCONNECTING:
					byeSetup();
					break;
        } 

    };

---

    public void byeSetup(){
		    	
		    	((TextView)findViewById(R.id.time)).setText(&quot;Bye Text&quot;);
		    	
		    	findViewById(R.id.keyboardimage).setOnClickListener(new OnClickListener() {
		            public void onClick(View v) {
		            	//Void the Button
		            }});
    }


CalledFromWrongThreadException: Only the original thread that created a view hierarchy can touch views

I have investigated this problem for months now, came up with different solutions to it, which I am not happy with since they are all massive hacks. I still cannot believe that a class that flawed in design made it into the framework and no-one is talking about it, so I guess I just must be missing something.

The problem is with `AsyncTask`. According to the documentation it 

&gt; &quot;allows to perform background
&gt; operations and publish results on the
&gt; UI thread without having to manipulate
&gt; threads and/or handlers.&quot;

The example then continues to show how some exemplary `showDialog()` method is called in `onPostExecute()`. This, however, seems **entirely contrived** to me, because showing a dialog always needs a reference to a valid `Context`, and an AsyncTask *must never hold a strong reference to a context object*.

The reason is obvious: what if the activity gets destroyed which triggered the task? This can happen all the time, e.g. because you flipped the screen. If the task would hold a reference to the context that created it, you&#39;re not only holding on to a useless context object (the window will have been destroyed and *any* UI interaction will fail with an exception!), you even risk creating a memory leak.

Unless my logic is flawed here, this translates to: `onPostExecute()` is entirely useless, because what good is it for this method to run on the UI thread if you don&#39;t have access to any context? You can&#39;t do anything meaningful here.

One workaround would be to not pass context instances to an AsyncTask, but a `Handler` instance. That works: since a Handler loosely binds the context and the task, you can exchange messages between them without risking a leak (right?). But that would mean that the premise of AsyncTask, namely that you don&#39;t need to bother with handlers, is wrong. It also seems like abusing Handler, since you are sending and receiving messages on the same thread (you create it on the UI thread and send through it in onPostExecute() which is also executed on the UI thread).

To top it all off, even with that workaround, you still have the problem that when the context gets destroyed, you have *no record* of the tasks it fired. That means that you have to re-start any tasks when re-creating the context, e.g. after a screen orientation change. This is slow and wasteful.

My solution to this (as [implemented in the Droid-Fu library][1]) is to maintain a mapping of `WeakReference`s from component names to their current instances on the unique application object. Whenever an AsyncTask is started, it records the calling context in that map, and on every callback, it will fetch the current context instance from that mapping. This ensures that you will never reference a stale context instance *and* you always have access to a valid context in the callbacks so you can do meaningful UI work there. It also doesn&#39;t leak, because the references are weak and are cleared when no instance of a given component exists anymore.

Still, it is a complex workaround and requires to sub-class some of the Droid-Fu library classes, making this a pretty intrusive approach.

**Now I simply want to know:** Am I just massively missing something or is AsyncTask really entirely flawed? How are your experiences working with it? How did you solve these problem?

Thanks for your input.


  [1]: https://github.com/mttkay/droid-fu/

Is AsyncTask really conceptually flawed or am I just missing something?

What I am trying to implement is basically a &quot;on ng repeat finished rendering&quot; handler. I am able to detect when it is done but I can&#39;t figure out how to trigger a function from it.

Check the fiddle:http://jsfiddle.net/paulocoelho/BsMqq/3/

JS

    var module = angular.module(&#39;testApp&#39;, [])
        .directive(&#39;onFinishRender&#39;, function () {
        return {
            restrict: &#39;A&#39;,
            link: function (scope, element, attr) {
                if (scope.$last === true) {
                    element.ready(function () {
                        console.log(&quot;calling:&quot;+attr.onFinishRender);
                        // CALL TEST HERE!
                    });
                }
            }
        }
    });
    
    function myC($scope) {
        $scope.ta = [1, 2, 3, 4, 5, 6];
        function test() {
            console.log(&quot;test executed&quot;);
        }
    }

HTML

    &lt;div ng-app=&quot;testApp&quot; ng-controller=&quot;myC&quot;&gt;
        &lt;p ng-repeat=&quot;t in ta&quot; on-finish-render=&quot;test()&quot;&gt;{{t}}&lt;/p&gt;
    &lt;/div&gt;

**Answer**:
Working fiddle from finishingmove: http://jsfiddle.net/paulocoelho/BsMqq/4/ 

Calling a function when ng-repeat has finished

I am using jQuery v.1.7.1 where the .live() method is apparently deprecated. 

The problem I am having is that when dynamically loading html into an element using:

    $(&#39;#parent&#39;).load(&quot;http://...&quot;); 

If I try and add a click event afterwards it does not register the event using either of these methods:

    $(&#39;#parent&#39;).click(function() ...); 

or

    // according to documentation this should be used instead of .live()
    $(&#39;#child&#39;).on(&#39;click&#39;, function() ...); 

What is the correct way to achieve this functionality? It only seems to work with .live() for me, but I shouldn&#39;t be using that method. Note that #child is a dynamically loaded element. 

Thanks. 

jQuery .live() vs .on() method for adding a click event after loading dynamic html

I want to do something like this in Java but I don&#39;t know the way:

When event &quot;object 1 say &#39;hello&#39;&quot; happens,
then object 2 responds to that event by saying &quot;hello&quot;.

Can somebody give me a hint or sample code?

Create a custom event in Java

I want to be able to call the following method after a specified delay.
 In objective c there was something like:

    [self performSelector:@selector(DoSomething) withObject:nil afterDelay:5];

Is there an equivalent of this method in android with java?
For example I need to be able to call a method after 5 seconds.

    public void DoSomething()
    {
         //do something here
    }

How to call a method after a delay in Android

I&#39;m converting my code from using `Handler` to `AsyncTask`. The latter is great at what it does - asynchronous updates and handling of results in the main UI thread.  What&#39;s unclear to me is how to handle exceptions if something goes haywire in `AsyncTask#doInBackground`. 

The way I do it is to have an error Handler and send messages to it. It works fine, but is it the &quot;right&quot; approach or is there better alternative?

Also I understand that if I define the error Handler as an Activity field, it should execute in the UI thread.  However, sometimes (very unpredictably) I will get an Exception saying that  code triggered from `Handler#handleMessage` is executing on the wrong thread. Should I initialize error Handler in `Activity#onCreate` instead? Placing `runOnUiThread` into `Handler#handleMessage` seems redundant but it executes very reliably.

AsyncTask and error handling on Android

I call multiple Handlers by new Handler().postDelayed(new Runnable().....
How can I stop it when I click on back? 

    public class MyActivity extends AppCompatActivity implements OnClickListener {
	
	    private Button btn;
        private Handler handler;
        private Runnable myRunnable;
		
    	@Override
	    public void onCreate(Bundle savedInstanceState) {
		    super.onCreate(savedInstanceState);	
    		btn = (Button) findViewById(R.id.trainingsstart);
    		btn.setOnClickListener(this);	
    	}

    	@Override
    	public void onClick(View v) {
    	    Handler handler =  new Handler();
	        Runnable myRunnable = new Runnable() {
	            public void run() {
                    // Things to be done
        	    }
    	    };

	        handler.postDelayed(myRunnable, 3000);
    	}
	
	    @Override 
    	public void onBackPressed() { 
	    	super.onBackPressed();
    		handler.removeCallbacks(myRunnable);
	    }	
	}

I have the problem that my Handlers haven&#39;t a name like &quot;myHandler&quot;. How can I handle it?

Thanks for help!



Now I got these error:

    03-28 17:47:03.662: E/AndroidRuntime(1961): FATAL EXCEPTION: main
    03-28 17:47:03.662: E/AndroidRuntime(1961): java.lang.NullPointerException
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at de.basti12354.tage.uebungen.Tag1.onBackPressed(Tag1.java:120)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.app.Activity.onKeyUp(Activity.java:2159)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.KeyEvent.dispatch(KeyEvent.java:2647)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.app.Activity.dispatchKeyEvent(Activity.java:2389)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchKeyEvent(PhoneWindow.java:1860)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$ViewPostImeInputStage.processKeyEvent(ViewRootImpl.java:3791)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:3774)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3379)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3429)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3398)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:3483)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3406)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:3540)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3379)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3429)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3398)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3406)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3379)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3429)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3398)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:3516)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.ViewRootImpl$ImeInputStage.onFinishedInputEvent(ViewRootImpl.java:3666)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.inputmethod.InputMethodManager$PendingEvent.run(InputMethodManager.java:1982)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.inputmethod.InputMethodManager.invokeFinishedInputEventCallback(InputMethodManager.java:1698)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.inputmethod.InputMethodManager.finishedInputEvent(InputMethodManager.java:1689)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.inputmethod.InputMethodManager$ImeInputEventSender.onInputEventFinished(InputMethodManager.java:1959)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.view.InputEventSender.dispatchInputEventFinished(InputEventSender.java:141)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.os.MessageQueue.nativePollOnce(Native Method)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.os.MessageQueue.next(MessageQueue.java:132)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.os.Looper.loop(Looper.java:124)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at android.app.ActivityThread.main(ActivityThread.java:5103)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at java.lang.reflect.Method.invokeNative(Native Method)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at java.lang.reflect.Method.invoke(Method.java:525)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
    03-28 17:47:03.662: E/AndroidRuntime(1961): 	at dalvik.system.NativeStart.main(Native Method)





Stop handler.postDelayed()

I&#39;m about creating an app using a `UINavigationController` to present the next view controllers.
With iOS5 there&#180;s a new method to presenting `UIViewControllers`:

    presentViewController:animated:completion:

Now I ask me why isn&#180;t there a completion handler for `UINavigationController`?
There are just 

    pushViewController:animated:


Is it possible to create my own completion handler like the new `presentViewController:animated:completion:` ?

Completion handler for UINavigationController &quot;pushViewController:animated&quot;?

I want to make an `eventHandler` that passes the event and some parameters. The problem is that the function doesn&#39;t get the element. Here is an example:

	doClick = function(func){
		var elem = .. // the element where it is all about
		elem.onclick = function(e){
			func(e, elem);
		}
	}
	doClick(function(e, element){
		// do stuff with element and the event
	});


The `elem` must be defined outside of anonymous function. How can i get the passed element to use within the anonymous function? Is there a way to do this?

And what about `addEventListener`? I don&#39;t seem to be able to pass the event through an `addEventListener` at all do I ?

**Update**

I seemed to fix the problem with &#39;this&#39;

	doClick = function(func){
		var that = this;
		this.element.onclick = function(e){
			func(e, that);
		}
	}

Where this contains `this.element` that i can access in the function.

**The addEventListener**

But i&#39;m wondering about the `addEventListener`:

    function doClick(elem, func){
		element.addEventListener(&#39;click&#39;, func(event, elem), false);
	}

Javascript event handler with parameters

Let&#39;s say that I want to perform some action every 10 seconds and it doesn&#39;t necessarily need to update the view. 

The question is: is it better (I mean more efficient and effective) to use timer with timertask like here:

    final Handler handler = new Handler();

    TimerTask timertask = new TimerTask() {
        @Override
        public void run() {
            handler.post(new Runnable() {
                public void run() {
                   &lt;some task&gt;
                }
            });
        }
    };
    timer = new Timer();
    timer.schedule(timertask, 0, 15000);
    }

or just a handler with postdelayed

    final Handler handler = new Handler(); 
    final Runnable r = new Runnable()
    {
        public void run() 
        {
            &lt;some task&gt;
        }
    };
    handler.postDelayed(r, 15000);


Also I would be grateful if you could explain when to use which approach and why one of them is more efficient than another (if it actually is).

Timertask or Handler

I have checked the official Android documentation/guide for `Looper`, `Handler` and `MessageQueue` . But I couldn&#39;t get it. I am new to android, and got very confused with these concepts. 

What is the relationship between Looper, Handler and MessageQueue in Android?

I am trying some thing new on Android for which I need to access the handler of the UI thread.

I know the following:

 1. The UI thread has its own handler
    and looper 
 2. Any message will be put
    into the message queue of the UI
    thread 
 3. The looper picks up the event
    and passed it to the handler 
 4. The handler handles the message and
    sends the specfic event to the UI

I want to have my service which has to get the UI thread handler and put a message into this handler.
So that this message will be processed and will be issued to the UI.
Here the service will be a normal service which will be started by some application.

I would like to know if this is possible.
If so please suggest some code snippets, so that I can try it.

Regards
Girish

Accessing UI thread handler from a service

I am trying to learn some programming related terms, and I often come over the word &quot;handler&quot;. Can anyone please explain what it means and when to use it?

What is a handler?

In response to a change, I have multiple related tasks that should run.
How do I write an Ansible handler with multiple tasks?

For example, I would like a handler that restarts a service only if already started:

    - name: Restart conditionally
      shell: check_is_started.sh
      register: result

    - name: Restart conditionally step 2
      service: name=service state=restarted
      when: result

How do I write an Ansible handler with multiple tasks?

In general terms of java, there are listeners &amp; handlers for events.  
I mean I use them unknowingly, just whichever is available in the API. 

My question is, in what case do we use listeners and in what case do we use handlers for events?

What&#39;s the difference between them? Characteristics??

I&#39;ve searched for reasons and I couldn&#39;t find a proper explanation for Java. 


What&#39;s the difference between Event Listeners &amp; Handlers in Java?

I have a worker thread that sits in the background, processing messages. Something like this:

    class Worker extends Thread {

        public volatile Handler handler; // actually private, of course

        public void run() {
            Looper.prepare();
            mHandler = new Handler() { // the Handler hooks up to the current Thread
                public boolean handleMessage(Message msg) {
                    // ...
                }
            };
            Looper.loop();
        }
    }

From the main thread (UI thread, not that it matters) I would like to do something like this:

    Worker worker = new Worker();
    worker.start();
    worker.handler.sendMessage(...);

The trouble is that this sets me up for a beautiful race condition: at the time `worker.handler` is read, there is no way to be sure that the worker thread has already assigned to this field!

I cannot simply create the `Handler` from the `Worker`&#39;s constructor, because the constructor runs on the main thread, so the `Handler` will associate itself with the wrong thread.

This hardly seems like an uncommon scenario. I can come up with several workarounds, all of them ugly:

1. Something like this:

        class Worker extends Thread {

            public volatile Handler handler; // actually private, of course
    
            public void run() {
                Looper.prepare();
                mHandler = new Handler() { // the Handler hooks up to the current Thread
                    public boolean handleMessage(Message msg) {
                        // ...
                    }
                };
                notifyAll(); // &lt;- ADDED
                Looper.loop();
            }
        }

    And from the main thread:

        Worker worker = new Worker();
        worker.start();
        worker.wait(); // &lt;- ADDED
        worker.handler.sendMessage(...);

    But this is not reliable either: if the `notifyAll()` happens before the `wait()`, then we&#39;ll never be woken up!

2. Passing an initial `Message` to the `Worker`&#39;s constructor, having the `run()` method post it. An ad-hoc solution, won&#39;t work for multiple messages, or if we don&#39;t want to send it right away but soon after.

3. Busy-waiting until the `handler` field is no longer `null`. Yep, a last resort...

I would like to create a `Handler` and `MessageQueue` on behalf of the `Worker` thread, but this does not seem to be possible. What is the most elegant way out of this?

How to create a Looper thread, then send it a message immediately?

I have an **&quot;open&quot;** animation and am using `Handler.postDelayed(Runnable, delay)` to trigger a **&quot;close&quot;** animation after a short delay. However, during the time between open and close, there is possibly another animation triggered by a click.

My question is, how would I cancel the **&quot;close&quot;** animation in the handler?

How to remove a runnable from a handler object added by postDelayed?

I am newbie to python. I was trying logging in python and I came across **No handlers could be found for logger** error while trying to print some warning through logger instance. Below is the code I tried

    import logging
    logger=logging.getLogger(&#39;logger&#39;)
    logger.warning(&#39;The system may break down&#39;)

And I get this error **No handlers could be found for logger &quot;logger&quot;**

What&#39;s confusing me is when I first try to print warning using `logging` and then through `logger` , it works fine, like

    &gt;&gt;&gt; import logging
    &gt;&gt;&gt; logging.warning(&#39;This is a WARNING!!!!&#39;)
    WARNING:root:This is a WARNING!!!!
    &gt;&gt;&gt; 
    &gt;&gt;&gt; logger.warning(&#39;WARNING!!!!&#39;)
    WARNING:logger:WARNING!!!!

Can someone throw some light on what&#39;s happening in second scenario? 


No handlers could be found for logger

I&#39;ll admit straight off that I&#39;m new to development and trying my hand at Android. I&#39;ve been trying to search the &#39;net to find advice on how to implement some &quot;Hold Button to Repeat Action&quot; - I&#39;ve created a custom numpad from buttons and want a backspace-like behaviour. Having got so far, I called upon a friend who hasn&#39;t coded Android before, but done lots of C# / Java and seems to know what he&#39;s doing.

The code below works just fine, but I feel it could be done more neatly.  I apologise if I&#39;ve missed bits out, but hopefully this explains my approach.  I think the onTouchListener is ok, but the way Threads are handled doesn&#39;t feel right.

Is there a better or more simple way to do this?

    public class MyApp extends Activity {
	
	private boolean deleteThreadRunning = false;
	private boolean cancelDeleteThread = false;
	private Handler handler = new Handler();
		
	public void onCreate(Bundle icicle) {
		super.onCreate(icicle);
		
		//May have missed some declarations here...
			
		Button_Del.setOnTouchListener(new OnTouchListener() {
			public boolean onTouch(View v, MotionEvent event) {
				
		       switch (event.getAction())
		       {
			       case MotionEvent.ACTION_DOWN:
			       {
			    	   handleDeleteDown();
			    	   return true;
			       }
			       
			       case MotionEvent.ACTION_UP:
			       {
			    	   handleDeleteUp();
			    	   return true;
			       }
			       
			       default:
			    	   return false;
		       }
		    }
	
			private void handleDeleteDown() {
	
				if (!deleteThreadRunning)
					startDeleteThread();
			}
	
			private void startDeleteThread() {

				Thread r = new Thread() {
					
					@Override
					public void run() {
						try {
							
							deleteThreadRunning = true;
							while (!cancelDeleteThread) {
								
								handler.post(new Runnable() {	
									@Override
									public void run() {
										deleteOneChar();
									}
								});
								
								try {
									Thread.sleep(100);
								} catch (InterruptedException e) {
									throw new RuntimeException(
										&quot;Could not wait between char delete.&quot;, e);
								}
							}
						}
						finally
						{
							deleteThreadRunning = false;
							cancelDeleteThread = false;
						}
					}
				};
				
				// actually start the delete char thread
				r.start();
			}
		});
	}
	
	private void handleDeleteUp() {
		cancelDeleteThread = true;
	}
	
	private void deleteOneChar()
	{
		String result = getNumberInput().getText().toString();
		int Length = result.length();
		
		if (Length &gt; 0)
			getNumberInput().setText(result.substring(0, Length-1));
			//I&#39;ve not pasted getNumberInput(), but it gets the string I wish to delete chars from
	}

Android - Hold Button to Repeat Action

What is the most accurate way to call a function every N milliseconds?

 - Thread with Thread.sleep
 - TimerTask
 - Handler with postDelayed

I modified [this example][1] using Thread.sleep and it&#39;s not very accurate.

I&#39;m developing a music app that will play sounds at a given BPM.  I understand it&#39;s impossible to create an entirely accurate metronome and I don&#39;t need to - just looking to find the best way to do this.

Thanks


  [1]: http://www.javacodegeeks.com/2011/07/android-game-development-game-loop.html

TimerTask vs Thread.sleep vs Handler postDelayed - most accurate to call function every N milliseconds?

in my app I&#39;m using IntentService for sending SMS.

    	@Override
	protected void onHandleIntent(Intent intent) {
		Bundle data = intent.getExtras();
		String[] recipients = null;
		String message = getString(R.string.unknown_event);
		String name = getString(R.string.app_name);
		if (data != null &amp;&amp; data.containsKey(Constants.Services.RECIPIENTS)) {
			recipients = data.getStringArray(Constants.Services.RECIPIENTS);
			name = data.getString(Constants.Services.NAME);
			message = data.getString(Constants.Services.MESSAGE);
			for (int i = 0; i &lt; recipients.length; i++) {
				if(!StringUtils.isNullOrEmpty(recipients[i])) {
					try {
						Intent sendIntent = new Intent(this, SMSReceiver.class);
						sendIntent.setAction(Constants.SMS.SEND_ACTION);
						PendingIntent sendPendingIntent = PendingIntent.getBroadcast(getApplicationContext(), 0, sendIntent, PendingIntent.FLAG_UPDATE_CURRENT);
						Intent deliveryIntent = new Intent(this, SMSReceiver.class);
						deliveryIntent.setAction(Constants.SMS.DELIVERED_ACTION);
						PendingIntent deliveryPendingIntent = PendingIntent.getBroadcast(getApplicationContext(), 0, deliveryIntent, PendingIntent.FLAG_UPDATE_CURRENT);
						SmsManager.getDefault().sendTextMessage(recipients[i].trim(), null, &quot;[&quot; + name + &quot;] &quot; + message, sendPendingIntent, deliveryPendingIntent);
					} catch (Exception e) {
						Log.e(TAG, &quot;sendTextMessage&quot;, e);
						e.printStackTrace();
						Toast.makeText(this, e.getMessage(), Toast.LENGTH_LONG).show();
						MainActivity.instance.writeToLogFile(e.getMessage(), System.currentTimeMillis());						
					}
				}
			}
		}
	}

when running the app, I get the following error:


    W/MessageQueue(7180): Handler (android.os.Handler) {42586468} sending message to a Handler on a dead thread
    W/MessageQueue(7180): java.lang.RuntimeException: Handler (android.os.Handler) {42586468} sending message to a Handler on a dead thread
    W/MessageQueue(7180): 	at android.os.MessageQueue.enqueueMessage(MessageQueue.java:294)
    W/MessageQueue(7180): 	at android.os.Handler.enqueueMessage(Handler.java:618)
    W/MessageQueue(7180): 	at android.os.Handler.sendMessageAtTime(Handler.java:587)
    W/MessageQueue(7180): 	at android.os.Handler.sendMessageDelayed(Handler.java:558)
    W/MessageQueue(7180): 	at android.os.Handler.post(Handler.java:323)
    W/MessageQueue(7180): 	at android.widget.Toast$TN.hide(Toast.java:367)
    W/MessageQueue(7180): 	at android.app.ITransientNotification$Stub.onTransact(ITransientNotification.java:55)
    W/MessageQueue(7180): 	at android.os.Binder.execTransact(Binder.java:351)
    W/MessageQueue(7180): 	at dalvik.system.NativeStart.run(Native Method)


My SMSReceiver is located in another class.
How can i solve this problems?
Thanks;
Eyal.

java.lang.RuntimeException: Handler (android.os.Handler) sending message to a Handler on a dead thread

I&#39;m new to JavaScript and programming in general, and I have some questions about objects and events.

Say I have an object:

    var computer = {
        keyboard: {}
    }


What I&#39;m looking for is a way to register events to the keyboard object:

    computer.keyboard.registerEvent( &quot;keyEscape&quot; );


Fire the event:

    computer.keyboard.dispatchEvent( &quot;keyEscape&quot; );


And create event handlers:

    computer.keyboard.addEventListener( &quot;keyEscape&quot;, function() {...} );

I know how to do this with DOM elements but not objects. Is this something that can be done in JavaScript (maybe with the help of JQuery)?

Even the slightest bit of guidance would be appreciated greatly.

Custom Events Model without using DOM events in JavaScript

I have come across both [Handlers][1] and [runOnUiThread][2] concepts. But to me it still seems to be a doubt as on which facts do they differ exactly. 

They both are intended to do UI actions from a background thread. But what are the factors that are to be considered while we choose among the two methods. 

For example consider a `Runnable` `Thread` which performs a web service in the background and now I want to update the UI. 

**What would be the best way to update my UI? Should I go for `Handler` or `runOnUiThread`?**

I still know I could use a `AsyncTask` and make use of `onPostExecute`. But I just want to know the difference. 


  [1]: http://developer.android.com/reference/android/os/Handler.html
  [2]: http://developer.android.com/reference/android/app/Activity.html#runOnUiThread%28java.lang.Runnable%29

All Handler Solutions on Gang of Coders

Total of 25 Handler Solutions