You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, download files, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!
If you have any problems with the registration process or your account login, please contact contact us.
If you are a developer who uses the .NET Compact Framework, you know that the CF tries to incorporate all of the larger .NET programming capabilites, while excluding items that most likely won't be used on a mobile device. This allows for the Compact Framework to be a small install or in the case of WM2003, embedded in ROM - so no install at all. However, in many cases something was left out that we still need.
There is an article over at MSDN Magazine by Alan Pulliam about how to use the .NET Compact Framework-only MessageWindow class, P/Invoke, and a few lines of code to use Windows subclassing to access native window handles and messages. i.e. add standard Tab key navigation to a Compact Framework-based application that runs on a Pocket PC. Pocket PCs Don't Have Keyboards...Or Do They?
First, let me start by explaining that I'm not the type who creates solutions in search of a problem. While this subclassing technique turned out to be an ideal solution for providing access to Windows messages in Compact Framework-based apps, I was actually trying to solve a very specific problem. I was developing an inventory application for a handheld barcode scanner running on a Windows Mobile™ 2002-based Pocket PC. This device was equipped with the standard stylus and touch screen, but also had an alphanumeric keypad. The client wanted to have custom navigation on the application forms, with the Enter key used in addition to the Tab key to advance focus to the next control on each form, and soft keys functioning like Back and Forward browser buttons to move to and from previous and next forms.
Any comments?
Linear Mode
