?? brew_touch.c
字號:
/*===========================================================================
FILE: brew_touch.c
===========================================================================*/
/*===============================================================================
INCLUDES AND VARIABLE DEFINITIONS
=============================================================================== */
#include "AEEModGen.h" // Module interface definitions
#include "AEEAppGen.h" // Applet interface definitions
#include "AEEShell.h" // Shell interface definitions
#include "AEEStdLib.h"
#include "AEEPointerHelpers.h"//觸摸屏
#include "brew_touch.bid"
/*-------------------------------------------------------------------
Applet structure. All variables in here are reference via "pMe->"
-------------------------------------------------------------------*/
// create an applet structure that's passed around. All variables in
// here will be able to be referenced as static.
typedef struct _brew_touch {
AEEApplet a ; // First element of this structure must be AEEApplet
AEEDeviceInfo DeviceInfo; // always have access to the hardware device information
// add your own variables here...
} brew_touch;
/*-------------------------------------------------------------------
Function Prototypes
-------------------------------------------------------------------*/
static boolean brew_touch_HandleEvent(brew_touch* pMe,
AEEEvent eCode, uint16 wParam,
uint32 dwParam);
boolean brew_touch_InitAppData(brew_touch* pMe);
void brew_touch_FreeAppData(brew_touch* pMe);
/*===============================================================================
FUNCTION DEFINITIONS
=============================================================================== */
/*===========================================================================
FUNCTION: AEEClsCreateInstance
DESCRIPTION
This function is invoked while the app is being loaded. All Modules must provide this
function. Ensure to retain the same name and parameters for this function.
In here, the module must verify the ClassID and then invoke the AEEApplet_New() function
that has been provided in AEEAppGen.c.
After invoking AEEApplet_New(), this function can do app specific initialization. In this
example, a generic structure is provided so that app developers need not change app specific
initialization section every time except for a call to IDisplay_InitAppData().
This is done as follows: InitAppData() is called to initialize AppletData
instance. It is app developers responsibility to fill-in app data initialization
code of InitAppData(). App developer is also responsible to release memory
allocated for data contained in AppletData -- this can be done in
IDisplay_FreeAppData().
PROTOTYPE:
int AEEClsCreateInstance(AEECLSID ClsId,IShell * pIShell,IModule * po,void ** ppObj)
PARAMETERS:
clsID: [in]: Specifies the ClassID of the applet which is being loaded
pIShell: [in]: Contains pointer to the IShell object.
pIModule: pin]: Contains pointer to the IModule object to the current module to which
this app belongs
ppObj: [out]: On return, *ppObj must point to a valid IApplet structure. Allocation
of memory for this structure and initializing the base data members is done by AEEApplet_New().
DEPENDENCIES
none
RETURN VALUE
AEE_SUCCESS: If the app needs to be loaded and if AEEApplet_New() invocation was
successful
EFAILED: If the app does not need to be loaded or if errors occurred in
AEEApplet_New(). If this function returns FALSE, the app will not be loaded.
SIDE EFFECTS
none
===========================================================================*/
int AEEClsCreateInstance(AEECLSID ClsId, IShell *pIShell, IModule *po, void **ppObj)
{
*ppObj = NULL;
if( ClsId == AEECLSID_BREW_TOUCH )
{
// Create the applet and make room for the applet structure
if( AEEApplet_New(sizeof(brew_touch),
ClsId,
pIShell,
po,
(IApplet**)ppObj,
(AEEHANDLER)brew_touch_HandleEvent,
(PFNFREEAPPDATA)brew_touch_FreeAppData) ) // the FreeAppData function is called after sending EVT_APP_STOP to the HandleEvent function
{
//Initialize applet data, this is called before sending EVT_APP_START
// to the HandleEvent function
if(brew_touch_InitAppData((brew_touch*)*ppObj))
{
//Data initialized successfully
return(AEE_SUCCESS);
}
else
{
//Release the applet. This will free the memory allocated for the applet when
// AEEApplet_New was called.
IAPPLET_Release((IApplet*)*ppObj);
return EFAILED;
}
} // end AEEApplet_New
}
return(EFAILED);
}
/*===========================================================================
FUNCTION SampleAppWizard_HandleEvent
DESCRIPTION
This is the EventHandler for this app. All events to this app are handled in this
function. All APPs must supply an Event Handler.
PROTOTYPE:
boolean SampleAppWizard_HandleEvent(IApplet * pi, AEEEvent eCode, uint16 wParam, uint32 dwParam)
PARAMETERS:
pi: Pointer to the AEEApplet structure. This structure contains information specific
to this applet. It was initialized during the AEEClsCreateInstance() function.
ecode: Specifies the Event sent to this applet
wParam, dwParam: Event specific data.
DEPENDENCIES
none
RETURN VALUE
TRUE: If the app has processed the event
FALSE: If the app did not process the event
SIDE EFFECTS
none
===========================================================================*/
static boolean brew_touch_HandleEvent(brew_touch* pMe, AEEEvent eCode, uint16 wParam, uint32 dwParam)
{
int x,y;
AECHAR *pChar;
int charLen;
AECHAR wsz[ 16 ];
AECHAR szText[] = {'H','e','l','l','o',' ','W','o', 'r', 'l', 'd', '\0'};
switch (eCode)
{
// App is told it is starting up
case EVT_APP_START:
// Add your code here...
IDISPLAY_ClearScreen(pMe->a.m_pIDisplay);
IDISPLAY_DrawText(pMe->a.m_pIDisplay, // Display instance
AEE_FONT_NORMAL, // Use BOLD font
szText, // Text - Normally comes from resource
-1, // -1 = Use full string length
0, // Ignored - IDF_ALIGN_CENTER
0, // Ignored - IDF_ALIGN_MIDDLE
NULL, // No clipping
IDF_ALIGN_CENTER | IDF_ALIGN_MIDDLE);//IDF_ALIGN_CENTER | IDF_ALIGN_TOP
IDISPLAY_Update (pMe->a.m_pIDisplay);
return(TRUE);
// App is told it is exiting
case EVT_APP_STOP:
// Add your code here...
return(TRUE);
// App is being suspended
case EVT_APP_SUSPEND:
// Add your code here...
return(TRUE);
// App is being resumed
case EVT_APP_RESUME:
// Add your code here...
return(TRUE);
// An SMS message has arrived for this app. Message is in the dwParam above as (char *)
// sender simply uses this format "//BREW:ClassId:Message", example //BREW:0x00000001:Hello World
case EVT_APP_MESSAGE:
// Add your code here...
return(TRUE);
// A key was pressed. Look at the wParam above to see which key was pressed. The key
// codes are in AEEVCodes.h. Example "AVK_1" means that the "1" key was pressed.
case EVT_KEY:
// Add your code here...
return(TRUE);
/*============================一下是對觸摸事件的處理================================================*/
/*
開發建議
a. 因為快速包不允許修改程序，盡量使同一個程序可以在觸摸屏事件定義不同的手機上都正常運行。例如利用配置文件。
case EVT_POINTER_DOWN:
case EVT_PEN_DOWN:
...處理...
break;
這種寫法在某些新手機上可能會有問題。為保證兼容性，一次點擊，在這些手 機上會同時發送POINTER,PEN這兩種事件。會有重復處理的問題。
b. 低版本的觸摸屏事件參數只包含位置信息。高版本的還包括是否雙擊這樣的額外信息。如果需要使用這些信息，最好自己編寫實現，避免高低版本處理不同。
c. 中斷返回時很可能接受不到Up事件，要注意對這種情況的處理。
d. 如果是將非觸摸屏版本改為觸摸屏版本的話。可以考慮利用原先的按鍵處理程序，例如將觸摸屏事件轉換為相應的按鍵事件處理。
e. 即使不是開發觸摸屏應用，也應在程序設計上有所考慮，方便以后擴充觸摸屏功能。例如自己寫控件上，即使現在只接受EVT_KEY,也應傳入eCode。
*/
/*
在手機處理觸摸屏事件中 也有不同，已測試的手機情況如下：
----------------------------------------
LG KW838 ：
同時發送EVT_POINTER_XXXXX和EVT_PEN_XXXXX。
可能是這款手機速度太快，測試員感覺是一次的觸摸，手機卻總是會發送兩次相同的事件。
Moto A1800 ：
發送EVT_PEN_XXXXX事件。
----------------------------------------
三星W599 ：
發送EVT_PEN_XXXXX事件，同時發送AVK_FUNCTION5按鍵事件。
輸入法小鍵盤會被ITextCtl控件擋住。
屏幕邊緣觸摸坐標與顯示坐標不一致，且偏離程度與高度有關。
---------------------------------------
三星W559 ：
發送EVT_PEN__W559_XXXXX事件，同時發送AVK_STOP按鍵事件。
輸入法小鍵盤會被ITextCtl控件擋住。
測試員傳送EVT_PEN_W559_XXXXX事件給BREW控件。但除了輸入法小鍵盤外，其余控件均不響應。
顯示坐標與觸摸感應坐標不一致
x(顯示)=x(觸摸)
y(顯示)≈y(觸摸) – 24
---------------------------------------
Coolpad C528 ：
發送EVT_PEN_XXXXX事件
IhtmlViewer控件不支持觸摸屏操作。
大顯C8100 ：
發送EVT_PEN_XXXXX事件
沒有EVT_PEN_MOVE事件
-------------------------------------
海信D90 :
同時發送EVT_POINTER_XXXXX和EVT_PEN_XXXXX事件。
但控件只處理EVT_PEN_XXXXXX事件。
軟鍵盤會出現在屏幕下方。ITextCtl要覆蓋到這個區域，軟鍵盤才會相應。（不十分確定）。
----------------------------------------
UT CD500 :
同時發送EVT_POINTER_XXXXX和EVT_PEN_XXXXX事件。
但控件只處理EVT_POINTER_XXXXXX事件。
阿爾卡特OT-S659 :
同時發送EVT_POINTER_XXXXX和EVT_PEN_XXXXX事件。
但控件只處理EVT_POINTER_XXXXXX事件。
============================================
3、 3.1.5模擬器注意事項
目錄或文件不要用中文名，全部小寫。
注意大小限制。Mif和模擬器使用的device都有關于文件大小的限制。
數據庫格式格式與2.X不同。（不確定）
當觸摸點從屏幕邊緣劃出屏幕外時，模擬器不會發出Up事件。而在有些真機上是會發出的。
*/
//在這里處理自己的事件
case EVT_PEN_UP:
case EVT_POINTER_UP:
DBGPRINTF("----Receive msg: EVT_POINTER_UP ---");
DBGPRINTF("-%s",(char*)dwParam);
break;
case EVT_PEN_DOWN:
case EVT_POINTER_DOWN:
DBGPRINTF("----Receive msg: EVT_POINTER_DOWN ---");
DBGPRINTF("-%s",(char*)dwParam);
AEE_POINTER_GET_XY((char*)dwParam, &x, &y); //取得屏幕觸點坐標 dwParam的高16位代表x的值。低16位 代表y值
//INET_NTOA(x,pChar,charLen);
WSPRINTF( wsz, sizeof( wsz ), L"X position=%d", x );
IDISPLAY_ClearScreen(pMe->a.m_pIDisplay);
IDISPLAY_DrawText(pMe->a.m_pIDisplay, // Display instance
AEE_FONT_NORMAL, // Use BOLD font
wsz, // Text - Normally comes from resource
-1, // -1 = Use full string length
80, // Ignored - IDF_ALIGN_CENTER
80, // Ignored - IDF_ALIGN_MIDDLE
NULL, // No clipping
IDF_ALIGN_CENTER);
WSPRINTF( wsz, sizeof( wsz ), L"Y position=%d", y );
IDISPLAY_DrawText(pMe->a.m_pIDisplay, // Display instance
AEE_FONT_NORMAL, // Use BOLD font
wsz, // Text - Normally comes from resource
-1, // -1 = Use full string length
80, // Ignored - IDF_ALIGN_CENTER
100, // Ignored - IDF_ALIGN_MIDDLE
NULL, // No clipping
IDF_ALIGN_CENTER);//IDF_ALIGN_CENTER | IDF_ALIGN_TOP
IDISPLAY_Update (pMe->a.m_pIDisplay);
DBGPRINTF("x=%d, y=%d", x, y);
if(x>200 && x < 240 && y>200 && y<240){ //固定區域觸摸響應
DBGPRINTF("soft key 2");
}
return(TRUE);
case EVT_PEN_MOVE:
case EVT_POINTER_MOVE:
DBGPRINTF("----Receive msg: EVT_POINTER_MOVE ---");
break;
return(TRUE);
// If nothing fits up to this point then we'll just break out
// If nothing fits up to this point then we'll just break out
default:
break;
}
return FALSE;
}
// this function is called when your application is starting up
boolean brew_touch_InitAppData(brew_touch* pMe)
{
// Get the device information for this handset.
// Reference all the data by looking at the pMe->DeviceInfo structure
// Check the API reference guide for all the handy device info you can get
pMe->DeviceInfo.wStructSize = sizeof(pMe->DeviceInfo);
ISHELL_GetDeviceInfo(pMe->a.m_pIShell,&pMe->DeviceInfo);
// Insert your code here for initializing or allocating resources...
// if there have been no failures up to this point then return success
return TRUE;
}
// this function is called when your application is exiting
void brew_touch_FreeAppData(brew_touch* pMe)
{
// insert your code here for freeing any resources you have allocated...
// example to use for releasing each interface:
// if ( pMe->pIMenuCtl != NULL ) // check for NULL first
// {
// IMENUCTL_Release(pMe->pIMenuCtl) // release the interface
// pMe->pIMenuCtl = NULL; // set to NULL so no problems trying to free later
// }
//
}
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -