Filed in archive
Opinion
, PDAs
, Useful Info
, Windows Mobile
by Rico Mossesgeld on October 16, 2006

The Windows Mobile Team has come clean, finally explaining the reasoning behind this weirdness. Turns out the Pocket PC OS is manages your gadget's memory automatically. So instead of closing a program when you tap that X, the OS just hides it, closing it only when it thinks you need more memory.
The problem was, since the earlier Windows Mobile devices didn't manage memory properly, it wouldn't free up memory when you really needed it. So everything would slow down, or even crash. All because that X wouldn't do what you though it would. Funny, huh?
Early adopters of the platform had to reset their device regularly, if only to make sure they had enough to get things done. At least more recent Windows Mobile Pocket PCs seem to do a better job of this, which is why they're faster and more responsive nowadays.
But I think the programmers of Windows Mobile should program the X to do what it's known to do: close a program. After all, when it comes to what's needed and what's not, the user usually knows best.
Wouldn't you agree? Thanks to Brighthand for the heads-up.
Update: If you really want applications to close when you tap that X, Magic Button may interest you.
Tags:
Tapping+X+Hides+Programs
Trackback: http://publish.creative-weblogging.com/publish/mt-tb.pl/39279
Mr Wong
Vote for Why "X" Never Marks the Spot in Windows Mobile:
|
Rating: 8.29 out of 7 vote(s) cast.
|
Subscribe
Marketplace
- mobile broadband
Use the search to look for other interesting posts
| RSS | See all blog subscribe options |
|
What is RSS? | |
| Yahoo! |
|
| Addthis |
|
| Bloglines |
|
| Newsletter | |
| Follow us on Twitter! |







