|
Honeywell sdk for Windows Mobile (6000 w 5) Copyright 2011 Honeywell International Inc
|
Sana | 26.12.2019 | Hajmi | 129,01 Kb. | | #5263 |
Honeywell SDK for Windows Mobile (6000 WM6.5) Copyright © 2011 Honeywell International Inc.
Notes:
· Please refer to the following resources for additional information regarding the Dolphin hardware and development tools:
· Dolphin Users Guide - located on the Dolphin User CD
· Dolphin SDK Online Help - located by default under Program Files | Honeywell
· Honeywell website: http://www.honeywellaidc.com/
· Microsoft Windows Mobile website: http://www.microsoft.com/windowsmobile/default.mspx
Release notes and known issues:
· Version 603 12/19/11
CameraAPI: Make focus mode setting before lens position.
BTPrintSample: Modify it to match JIRAID 59WM6-483.
· Version 602 10/18/11
Modify version information.
· Version 602A2 9/22/11
Rename ScanCam… to ScanMan…
Modify help content from Rod's feedback.
Add ScanManSample vcproj file missed files
Add SwiftDecoder manual shortcut.
Resolve ScanManSample application exit abnormal when invoke SDDecode.
Resolve JIRAID 59WM6-423. Project may open with incorrect Assemblies referenced. Side by Side SDK Install Issue due to invalid Hint Paths in HSM samples.
· Version 602A1 8/15/11
Add ScanCam SDK including all assemblies, samples and help support VS 2008 and managed components support Compact Framework 3.5.
· Version 601 6/10/11
The DecodeComponent sample gives 2 "Object reference not set to an instance of an object" warnings in Form1.designer.cs, which in turn makes the designer fail if you try to open the form.
The DecodeAssembly sample doesn't work.
· Version 600R1 5/30/11
Add the topic of HHPWirelessManager to the document Honeywell SDK for Windows Mobile (6000).
SDK renamed to avoid collision with other WM 6 SDK. The name is Honeywell SDK for Windows Mobile (6000). The install dir is Program Files\Honeywell\SDK for Windows Mobile (6000).
SDK Lib and Header files are moved from 'Program Files\Windows Mobile 6 SDK\PocketPC' to ‘Program Files\Honeywell\SDK for Windows Mobile (6000)\Lib\' and Program Files\Honeywell\SDK for Windows Mobile (6000)\Include\'.
Add a shortcut “Launch Visual Studio 2008” to launch Visual Studio 2008 which sets the environment to contain the SDK Lib and Header files path.
· Version 600B3 5/16/11
Merge “Honeywell SDK for Windows Mobile 6.0” document into VS2008 help contents while installing the SDK package.
· Version 600B2 5/3/11
Merge “.NET Reference Help Documentation” into VS2008 help contents and remove .NET Reference Help Documentation shortcut.
Please run as administrator when in Windows 7 OS.
· Version 600B1 4/19/11
Re-add cabs which can be found at the following location: "\Honeywell\SDK for Windows Mobile 6.0\Cabs.
Fixed bugs: The Backlight related settings updated in DeviceConfig.exm do not reflect in Backlight settings applet after warmboot.
The Backlight, Power related settings displayed in DeviceConfig.exm do not match with the values available in Backlight and Power settings applets.
Update deviceconfig.exm to support MobiConrtol version 8.
Synchronize symblogy from ScanDemo and remove some unsupported symbology.
Symbologies related settings from ScanDemo are not getting saved as expected
The barcode can be decoded successfully while we set the value of minimum length larger than maximum length in symbology settings.
The addenda separator for UPC-A is still invalid even though we check “included addenda separator” box, instead,”Addenda Required” gets separator feature.
Regedit registry tree should scroll with gestures.
· Version 600A2 3/18/11
Modify Scan key code from 0x87 to 0x2A
Remove cabs which can be found at the following location: "\Honeywell\SDK for Windows Mobile 6.0\Cabs.
· Version 600A1 3/15/11
All assemblies, samples and help support VS 2008 and managed components support Compact Framework 3.5.
Samples
VC samples:
BTPrintSample
DecodeSample
DeviceInfoSample
KeySample
LedSample
PowerManagementSample
VC# samples:
BTPrintSample
DecodeAssembly
DecodeComponent
GPRSSample
PowerManagementSample
RFSample
Known Issues:
There are still issues for APIs of system events in SDK which can not get notifications from low level libraries. This issue will be confirmed in next release.
|
| |