文件列表:

CALLLOG\ADDREJECTEDCALL\dirs (653, 2006-11-16)
CALLLOG\ADDREJECTEDCALL\DLL\makefile (868, 2006-11-16)
CALLLOG\ADDREJECTEDCALL\DLL\Override.cpp (750, 2006-11-16)
CALLLOG\ADDREJECTEDCALL\DLL\Override.def (11, 2006-09-19)
CALLLOG\ADDREJECTEDCALL\DLL\Override.rc (1046, 2006-11-16)
CALLLOG\ADDREJECTEDCALL\DLL\PpcMissed.bmp (1334, 2006-09-19)
CALLLOG\ADDREJECTEDCALL\DLL\resource.h (924, 2006-11-16)
CALLLOG\ADDREJECTEDCALL\DLL\sources (833, 2006-11-16)
CALLLOG\ADDREJECTEDCALL\DLL\TpcMissed.ico (2478, 2006-09-19)
CALLLOG\ADDREJECTEDCALL\DLL (0, 2008-07-21)
CALLLOG\ADDREJECTEDCALL\EXE\AddRejectedCall.cpp (7487, 2006-11-16)
CALLLOG\ADDREJECTEDCALL\EXE\makefile (869, 2006-11-16)
CALLLOG\ADDREJECTEDCALL\EXE\sources (888, 2006-11-16)
CALLLOG\ADDREJECTEDCALL\EXE (0, 2008-07-21)
CALLLOG\ADDREJECTEDCALL (0, 2008-07-21)
CALLLOG\CALLCOST\ADDCALLCOST\AddCallCost.cpp (6788, 2006-11-16)
CALLLOG\CALLCOST\ADDCALLCOST\makefile (869, 2006-11-16)
CALLLOG\CALLCOST\ADDCALLCOST\sources (973, 2006-11-16)
CALLLOG\CALLCOST\ADDCALLCOST (0, 2008-07-21)
CALLLOG\CALLCOST\CallCost.cpp (13828, 2006-11-16)
CALLLOG\CALLCOST\CallCost.h (2717, 2006-11-16)
CALLLOG\CALLCOST\CallCostCntrl.cpp (7324, 2006-11-16)
CALLLOG\CALLCOST\CallCostCntrl.h (1531, 2006-11-16)
CALLLOG\CALLCOST\CallLog.cpp (17216, 2006-11-16)
CALLLOG\CALLCOST\CallLog.def (75, 2006-09-19)
CALLLOG\CALLCOST\dirs (670, 2006-11-16)
CALLLOG\CALLCOST\MyResources.h (796, 2006-11-16)
CALLLOG\CALLCOST\PPC\makefile (869, 2006-11-16)
CALLLOG\CALLCOST\PPC\PhoneDialogCDMA.rc (15148, 2006-11-16)
CALLLOG\CALLCOST\PPC\PhoneDialogGSM.rc (22283, 2007-03-05)
CALLLOG\CALLCOST\PPC\sources (1289, 2006-11-16)
CALLLOG\CALLCOST\PPC (0, 2008-07-21)
CALLLOG\CALLCOST\TPC\makefile (869, 2006-11-16)
CALLLOG\CALLCOST\TPC\phonedialog.rc (4787, 2006-11-16)
CALLLOG\CALLCOST\TPC\sources (1260, 2006-11-16)
CALLLOG\CALLCOST\TPC (0, 2008-07-21)
CALLLOG\CALLCOST (0, 2008-07-21)
CALLLOG\dirs (668, 2006-11-16)
... ...

This is a sample showing how to use the PHCanvas APIs to add data to a new field in the Call Log database. The example illustrates how to combine this with displaying UI that uses the new data added. If you would like to add this to the phone application, simply build in this directory, then add the following reg keys to platform.reg: [HKEY_LOCAL_MACHINE\Init] "Launch75"="AddCallCost.exe" [HKEY_LOCAL_MACHINE\Security\Phone\Skin] "Enabled"=dword:1 [HKEY_LOCAL_MACHINE\Comm\Samples\CallLog\CallRates] "PeakRate"=dword:10 Also add the following to platform.bib: AddCallCost.exe $(_FLATRELEASEDIR)\AddCallCost.exe MISC SR For Pocket PCs, also do the following: Add the following to platform.reg: [HKEY_LOCAL_MACHINE\Security\Phone\Skin] "ext"="CallLogPPC.dll" Add the following to platform.bib: CallLogPpc.dll $(_FLATRELEASEDIR)\CallLogPpc.dll MISC SR For Smartphones, also do the following: Add the following to platform.reg: [HKEY_LOCAL_MACHINE\Security\Phone\Skin] "ext"="CallLogTPC.dll" Add the following to platform.bib: CallLogTpc.dll $(_FLATRELEASEDIR)\CallLogTpc.dll MISC SR Expectations: AddCallCost.exe will be launched during device initialization before CDial.exe and CProg.exe are launched. This application will add the new call cost property to the Call Log database then unregister itself from device initialization. CProg.exe will load the appropriate CallLog*.dll specified in the registry then whenever the last call data for the Phone application is updated, CallLog*.dll will compute the cost of the last call and add the cost to the Call Log database. When the last state of an ended call is displayed, CallLog*.dll will also display the cost of the last call. Exceptions and Assumptions made in the sample: Call cost is computed simply by using the rate provided in the registry. OEMs and MOs (Mobile Operators) wanting to compute per call costs for retail devices should consider using the RILCOSTINFO APIs instead of storing rate data in the registry. The registry value HKLM\Init,"Launch75" is not already defined. "Launch75" comes before the corresponding LaunchXX strings for CDial.exe and CProg.exe but after LaunchXX strings for critical system programs. AddCallCost.exe, CallLogPpc.dll, and CallLogTpc.dll can be digitally signed by the OEM to allow editing of registry data under the protected HKLM\Init and HKLM\Comm registry keys. Only portrait views are updated with the new call cost control. It is left as an exercise for the reader to update landscape views if desired. If the registry entries and files are applied manually then the device should be rebooted before testing to ensure that the sample files are loaded. Important notes regarding usage of HKLM\Init: This program adds a new field to the Call Log database to track per call costs. In order for this program to succeed, it must be executed before cdial.exe or cprog.exe are run or else the Call Log database will be in use and a sharing violation will occur when the program tries to add the new field. It is recommended that this program be added to HKLM\Init under the value name "Launch75" using a REG_SZ value data equal to this program's filename. 75 has been selected so that this function launches before user applications are executed but after critical system programs such as services.exe have been started. In general, it is highly discouraged to modify values in HKLM\Init unless timing issues require it. Performance and/or usability problems can occur if existing entries are overwritten, moved, or needed resources are put in use unexpectedly. Programs that are not timing sensitive but require execution during bootup initialization should be placed in the startup folder on the device. If a program must be executed before one or more native Windows Mobile applications, then great care should be taken to ensure that the program utilizes an unused value name and that it frees all resources opened when no longer needed. Important notes regarding the addition of new fields to the Call Log database: This program just adds a new UINT field to the Call Log database. It is possible to add a large number of new fields of differing data types. Great care should be taken to prevent so much data from being added that persistent store is filled up after many calls have been made. Call History will save up to 300 records.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：