http://www.leghumped.com/blog/2009/07/31/wpf-changing-input-focus-to-hidden-elements/ Coding snippets, tutorials and procrastinations about C#, Java and Linux. Mon, 28 Jun 2010 09:06:40 +0000 hourly 1 http://wordpress.org/?v=3.3 http://www.leghumped.com/blog/2009/07/31/wpf-changing-input-focus-to-hidden-elements/comment-page-1/#comment-5736 cretz Sat, 29 Aug 2009 10:49:47 +0000 http://leghumped.com/blog/?p=363#comment-5736 In my opinion, the solution with using the dispatcher invoke is better, because with your solution you have to remember to remove the event handler. The dispatcher code is clean and leaves no "traces" that can affect garbage collection. There is no cross-thread access in your case, because you don't set the focus from another thread (in that case your solution would not work at all). It's just delaying the execution of your code until the next layout pass is completed, so that your control is indeed visible. The dispatcher offers a way to schedule some code to be executed in the UI thread's infinite loop (priorities specify where in the loop iteration your code is called). In my opinion, the solution with using the dispatcher invoke is better, because with your solution you have to remember to remove the event handler. The dispatcher code is clean and leaves no “traces” that can affect garbage collection. There is no cross-thread access in your case, because you don’t set the focus from another thread (in that case your solution would not work at all). It’s just delaying the execution of your code until the next layout pass is completed, so that your control is indeed visible.
The dispatcher offers a way to schedule some code to be executed in the UI thread’s infinite loop (priorities specify where in the loop iteration your code is called).

]]>