Windows Mobile 6.5開(kāi)發(fā)環(huán)境搭建以及變化
搭建開(kāi)發(fā)環(huán)境，按照以下順序安裝。
◆安裝Visual Studio 2008(我安裝的試用的Team Suite版：VS2008TeamSuite90DayTrialCHSX1429243.iso)
◆安裝Microsoft ActiveSync 4.5.msi
◆安裝Windows Mobile 6 Professional SDK Refresh.msi(如果需要6.0版本的中文模擬器，需要安裝中文包：Windows Mobile 6 Professional Images (CHS).msi)
◆安裝Windows Mobile 6.5 Professional Developer Tool Kit (CHS).msi
如下圖，第一項(xiàng)QVGA即是6.5版本320x240屏幕的模擬器，高亮的一項(xiàng)的是真機(jī)，當(dāng)你需要在真機(jī)上調(diào)試時(shí)使用這項(xiàng)，可見(jiàn)6.5版本的開(kāi)發(fā)工具包并沒(méi)有帶真機(jī)調(diào)試項(xiàng)：
2.讓我們來(lái)看下Windows Mobile 6.5 Professional在開(kāi)發(fā)方面的變化。
Today Plug-in
你為6.5以前版本編寫的今日插件，仍然可以在6.5版本使用，6.5的策略讓默認(rèn)方案與其它子項(xiàng)互斥，當(dāng)你選中自己的插件時(shí)，默認(rèn)方案前面的勾將自動(dòng)去掉。右下圖顯示的即是默認(rèn)方案。
6.5版本改變的部分是：現(xiàn)在不允許把你自己編寫的插件的Type設(shè)為5，當(dāng)你設(shè)置為5的時(shí)候，系統(tǒng)會(huì)把你改回成4。
關(guān)于4和5在6.5以前版本差距還是很大的，請(qǐng)看我的筆記：
HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items下的Type為DWORD類型。
|
If the value of Type is 4, a custom plug-in is added to the Today Screen. If the value of Type is 5, the plug-in is a custom pinned plug-in. |
我自己編寫的插件設(shè)置為5的時(shí)候就解決了橫豎屏切換太慢問(wèn)題，慢的原因是Type為4的插件，每次橫豎屏切換，系統(tǒng)都會(huì)發(fā)送4次WM_PAINT消息!微軟在6.5版本優(yōu)化了這個(gè)問(wèn)題。下圖就是優(yōu)化之后的當(dāng)橫豎屏切換時(shí)系統(tǒng)發(fā)送的消息截圖：
Type另外還有以下值：
|
If the value of Type is 0, it indicates a reserved plug-in that displays the device owner information is added to the Today Screen. If the value of Type is 1, it indicates a reserved plug-in that displays the Appointments is added to the Today Screen. If the value of Type is 2, it indicates a reserved plug-in that displays the Mail is added to the Today Screen. If the value of Type is 3, it indicates a reserved plug-in that displays the Tasks is added to the Today Screen. If the value of Type is 6, the plug-in is a custom permanent pinned plug-in. |
說(shuō)到為什么使用蜂窩式菜單，記得我以前看過(guò)一篇文章有介紹，因?yàn)檎呅慰梢允褂|摸面積最大(相連的)。
| “A grid is the most efficient method to pack as many squares into an area as possible, but not for circles. The mathematically most efficient method to arrange non-overlapping circles - a problem called “sphere packing” - is actually and as you might have guessed by now, hexagonal. ” |
Windows下面并不能實(shí)現(xiàn)真正的窗口透明，目前我們開(kāi)發(fā)的應(yīng)用程序都是采用將下一個(gè)窗口的DC先在當(dāng)前窗口繪制一遍，實(shí)現(xiàn)透明按鈕也是這個(gè)道理，其實(shí)都是偽透明，那么任何實(shí)現(xiàn)真正透明的窗口?這個(gè)問(wèn)題我的繼續(xù)思考，不知讀者您能否解答^^
Gesture(手勢(shì)) APIs
|
A new set of APIs is being introduced that will enable application developers to take advantage of the new Windows Mobile 6.5 touch gesture framework. The gesture APIs allow an application to handle touch gesture input and provide a visually consistent experience with the rest of the device UI. The APIs are defined in the following header files: Note that the gesture APIs are only available on the Windows Mobile Classic and Professional SKUs. The headers and libraries are installed in the Windows Mobile SDK\Pocket PC\ folder. Samples that make use of these APIs are installed into the Windows Mobile 6.5 Developer Tool Kit\Samples\ folder. |
內(nèi)核以及驅(qū)動(dòng)開(kāi)發(fā)部分沒(méi) 有太多變化，因?yàn)樗匀皇腔赪indows CE 5.x系統(tǒng)。當(dāng)Windows Mobile 7.0推出時(shí)，因?yàn)槭腔赪indows CE 6.0系統(tǒng)，所以驅(qū)動(dòng)編寫也將發(fā)生大的變化。Windows CE發(fā)生的兩次大的內(nèi)核變化，一次是Windows CE 3.0，一次就是現(xiàn)在的Windows CE 6.0。下面討論的是Windows Mobile 6.5帶來(lái)的部分新功能。
3.Windows Mobile 6.5 Developer Tool Kit自帶的Samples，全部都是介紹Gesture的使用。
第一個(gè)例子
Code Sample Name: Gesture Metrics Sample
Feature Area: Touch
Description:
This sample demonstrates how to use the Gesture APIs. More specifically, it
demonstrates:
- use of RKGetGestureMetrics
- handling WM_GESTURE GID_HOLD, GID_SELECT and GID_DOUBLESELECT messages
This sample was designed to show how to use RKGetGestureMetrics and interpret
its results.
This example also shows how to handle GID_HOLD, GID_SELECT and GID_DOUBLESELECT
messages.
Relevant APIs/Associated Help Topics:
RKGetGestureMetrics
RKGetGestureInfo
GESTUREMETRICS
WM_GESTURE
第二個(gè)例子
Code Sample Name: Code Sample Name: Physics Engine Sample
Feature Area: Touch
Description:
This sample demonstrates how to use the Gesture APIs. More specifically, it
demonstrates:
- use of Physics Engine
- handling WM_GESTURE GID_PAN, GID_SCROLL and GID_END
This example shows how to handle gesture scrolling and how to properly use
Physics Engine.
Relevant APIs/Associated Help Topics:
RKCreatePhysicsEngine
RKQueryPhysicsEngine
RKDestroyPhysicsEngine
RKGetGestureInfo
PHYSICSENGINESTATE
PHYSICSENGINEINIT
WM_GESTURE
第三個(gè)例子
Code Sample Name: WAG Sample
Feature Area: Touch
Description:
This sample demonstrates how to use the Gesture APIs. More specifically, it
demonstrates:
- use of Window Auto Gesture API
This example shows how to handle gesture scrolling using Window Auto Gesture API.
Relevant APIs/Associated Help Topics:
RKSetWindowAutoGesture
RKGetAnimateMessageInfo
WAGINFO
ANIMATEMESSAGEINFO
【編輯推薦】
