Microsoft windows pocket pc 2003 2nd edition

I'd also suggest making sure you create and destroy the wait cursor on the UI thread, or you are asking for issues with it not appearing or being removed. The fact that it works or seems to on the emulator is an accident of implementation - like you are seeing the behavior will be inconsistent as the message pump is not really running while in your event handler - this is why you need a call to refresh to see the text change in your loop.

The above links are not specific to the compact framework - not all things discussed are currently supported but conceptually the ideas are what you need to understand. I'd also suggest that you take a look at the topic of "Programming by Coincidence" from "Pragmatic Programmer", unfortunately, it seems like you got caught in one, like we all seem to every now and then.

In CF 1. In any case, after reading this little excerpt, it makes me question and try to understand oddities like what you are experiencing - hope it helps! Are you using. NET CF v1 or v2? In v2 your code should have thrown a NotSupportedException when you tried to alter the label text from a non-UI thread. Although you're seeing the problem on one device but not another, I believe the problem is universally resolvable.

Part of the issue is that even with doing the thread. In my experience, if you have to do a long-running task on the main thread I agree with others that using an alternate thread for the long-running task is the best choice , a couple of calls to Application.

DoEvents can help a great deal. Calling Application. DoEvents pumps the message queue and in my experience making 2 consecutive calls to it immediatly after performing some operation that affects the UI will generally allow the UI to update. Using Application. DoEvents in this way is a bit of a hack, but can be really useful when you need to get something working quickly and don't have time to deal with the potential issues of splitting a task out to a different thread.

The content you requested has been removed. Learn More. Ask a question. Quick access. Search related threads. Remove From My Forums. Users will be able to go into Settings and change the screen orientation on the fly. It can be operated either be in portrait, landscape for right-handed users, or landscape for left-handed users.

All the standard applications now have both portrait and landscape versions. Microsoft has also released an updated Windows Mobile Developer Resource Kit with the information developers need. Naturally, there is no way an operating system upgrade can make current bypixel screens into bypixel ones. Update: The latest information on when HP and Dell will be releasing updates for current Pocket PC models is available in this article. Perhaps a better name for this would be pixel quadrupling because each pixel of an application designed for a by screen will be replaced by four new ones, which will allow the app to be displayed twice as tall and twice as wide.

Of course, there will be a session at Mobile DevCon on how to write applications that take full advantage of the new resolution.

Though the extra space on a VGA screen is a welcome change, no one wants this to come at the cost of unreadably small fonts.

Microsoft has included in the Second Edition a Settings panel which will include a slider to that allows the user to control the size of the font. Wednesday, April 19, PM. Please check that you have done following things 1. Cradle the emulator using Device Emulator Manager. Hope this helps. Tuesday, March 21, PM. Hello I checked the post you are talking about but I did not see any informationh that can help me for configuring the emulator to test mobile web applications. Did I miss something in the post?

Let me know please thanks. Is it possible for you to please post a sample app?