Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 31 Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 37 Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 43 Warning: strpos(): needle is not a string or an integer in /customers/a/f/c/fjorden.se/httpd.www/joel/index.php on line 49 Blog by Joel Fjordn a.k.a. Will o Wisp - No Keyboard Input in Modeless WPF Window
No Keyboard Input in Modeless WPF Window 
Tuesday, March 11, 2008, 06:24 PM - WPF
Today I encountered the weirdest problem, when showing a WPF Window from a Windows Forms application. When writing letters and numbers into a textbox nothing happened, but space and backspace together with shortcuts for Cut, Copy and Paste worked as expected.

I first thought there must be some problem with my data template, but when showing it from a WPF application everything worked just fine. My next instant thought was that there must be some message filter, in the Windows Forms application, stealing the keyboard input.

I then created a new Windows Forms application and brought up the modeless WPF Window from there, by calling Show, only to notice the same problem. I then changed to a modal window, by calling ShowDialog instead, and suddenly everything responded as it should.

It was time to start some Google:ing

The solution, to my big surprise, was to explicitly enable keyboard input from Windows Forms, by calling the static method ElementHost.EnableModelessKeyboardInterop. This call takes a Window as parameter and essentially registers an input hook with the Windows Forms application object, running the message loop, and calls ComponentDispatcher.RaiseThreadMessage. The call to EnableModelessKeyboardInterop can be made in the constructor, if the Window is inherited, or simply before calling the Show method.

For more information read about Sharing Message Loops Between Win32 and WPF.
4 comments ( 103 views )   |  related link

I Can See The Light 
Monday, February 18, 2008, 07:31 AM - Code Style Enforcer
Developer Express now seems to have fixed the deadlock issue during background code analysis, in DXCore 2.5+. I have received one of their daily build version containing this fix and I will try it more thoroughly this week, but it looks very promising.

I now hope that they will merge these changes into DXCore 3.0+ also.
1 comment ( 5 views )   |  related link

Stuck in the Middle 
Tuesday, January 29, 2008, 07:33 AM - Code Style Enforcer
Unfortunately Ive ran into some problems with my optimization plans and DXCore 3.0+ as well. Im really satisfied with my optimization code for Code Style Enforcer, but unfortunately DXCore doesnt work very well with background thread analysis, resulting deadlock related situations.

I was then informed by DevExpress that the new DXCore 3.0+ version was supposed to have special support for background thread analysis through the new code issue provider model. This, on the other hand, proved to be too much beta still since it didnt behave as expected.

Right now Im waiting for the DevExpress support team to analysis my code and the threading issues with DXCore 2.5+. The other alternative is to wait for a newer and more final version of DXCore 3.0+ and hopefully the background thread analysis will be good enough there, even though Im rather skeptical about it right now.

The optimization release is therefore put on hold for now, so I might look into some other issues first. Right now I feel in need of a good vacation though and therefore Im leaving for Florida on Friday. I can only hope that Ill get back with a lot of new enthusiasm :)!!!
2 comments ( 80 views )   |  related link

Code Style Enforcer and DXCore Version 3 
Sunday, January 6, 2008, 04:36 PM - Code Style Enforcer
DXCore version 3 is now available for download, but currently version 2 is the only supported version by Code Style Enforcer. The next release of CSE will be a performance upgrade, where optimizations have been made to the code rules checking engine, i.e. read previous log post.

After that I will begin targeting Code Style Enforcer against the new version 3 of DXCore, in order to use some new nice features of that release. This means that DXCore version 3 will soon be a requirement instead of version 2.

3 comments ( 133 views )   |  related link

Optimizing for a New Year 
Monday, December 31, 2007, 11:55 AM - Code Style Enforcer
Whats going on with Code Style Enforcer, you might ask?! Well, lately Ive been investigating performance issues related to CSE. In my team at work, some team members have been experiencing lag in Visual Studio when typing or scrolling in the code editor. It turned out that it had to do with CSE, since I do the code rule violations check on the DXCore Paint event, which occurs quite often. The lag most often occurs for big solutions and/or having a lot of event handlers.

Ive now redesigned when and how the code rule violations are checked, by utilizing the DXCore Parse event together with asynchronous calls. Im almost done with the optimization and hopefully we can try it out in our team in the upcoming week.

A new release can therefore be expected in early January, which will perform a lot better, but unfortunately wont have a lot of new features, if any at all.

Happy New Year!!!
5 comments ( 67 views )   |  related link

Back Next