New (14. july 2009):

• Added ArmV4 version as needed to use the tool on 700 color devices
  Although the tool is mainly targetting ITC WM5 devices it is also usefull to map keys on ITC WM2003 devices as the 700 color series. The remapper for the WM2003 devices does not offer all possibly mappings and so DirectKeyUI may be usefull for you.
• Added source code as of 29. june 2009
• Fixed some bugs in v1.2

After you started the tool, you select the plane and then the key to reassign. Please note, that not all values are mapped to keys. For example the first and last two entries near ‘Select Key’ are not of use on CN3′s.

Here I selected the third key entry, which is the upper left blue side key on the CN3 I tested here. Then I select VK_F22 as the new VK value.

You have to save each change immediately, if you like to have it applied.

As F22 is mapped to Lock function, the device is now locked immediately, if you press the upper button on the left side of the CN3.

Now start playing with the tool. You can assign VK values, events, multi keys and app button to any of the direct keys. Please do not use undefined values as 0×02, 0×04, 0×06 and -undef- as Key Type.

This is for testing and/or demo purpose only. Watch your step when playing with the tool.

DOWNLOAD:DirectKeyUI Windows Mobile 5/6 Executable - (Hits: 281, size: 72.19 KB)
DOWNLOAD:DirectKeyUI Windows Mobile 2003/5/6 CE4,5 VS2005 Source v1.2 - (Hits: 212, size: 170.25 KB)
DOWNLOAD:DirectKeyUI Windows CE4/5 - Mobile 5/6 Executable, v1.2 - (Hits: 182, size: 72.05 KB)
DOWNLOAD:DirectKeyUI Windows CE4 - Mobile 2003 Executable, v1.2 - (Hits: 179, size: 73.56 KB)

Bookmark It

Customer wants to use SAP ITS Mobile with Intermec Browser on CN3 and iBrowse on 700 color. The problem we found is, that intermec browser uses different META tags than iBrowse did. As you know, Intermec Browser is the successor of iBrowse, but it is not available for 700 color devices.

The META tags causing problems are the ones for checking/processing function keys:

<META HTTP-Equiv=”IB_OnKey0x70″ content=”Javascript:setFKey(’1′);”>

<META HTTP-Equiv=”IB_OnKey0x71″ content=”Javascript:setFKey(’2′);”>

<META HTTP-Equiv=”IB_OnKey0x72″ content=”Javascript:setFKey(’3′);”>

<META HTTP-Equiv=”IB_OnKey0x73″ content=”Javascript:setFKey(’4′);”>

<META HTTP-Equiv=”IB_OnKey0x74″ content=”Javascript:setFKey(’5′);”>

<META HTTP-Equiv=”IB_OnKey0x75″ content=”Javascript:setFKey(’6′);”>

<META HTTP-Equiv=”IB_OnKey0x76″ content=”Javascript:setFKey(’7′);”>

<META HTTP-Equiv=”IB_OnKey0x77″ content=”Javascript:setFKey(’8′);”>

<META HTTP-Equiv=”IB_OnKey0x78″ content=”Javascript:setFKey(’9′);”>

<META HTTP-Equiv=”IB_OnKey0x79″ content=”Javascript:setFKey(’10′);”>

<META HTTP-Equiv=”IB_OnKey0x7A” content=”Javascript:setFKey(’11′);”>

<META HTTP-Equiv=”IB_OnKey0x7B” content=”Javascript:setFKey(’12′);”>

<META HTTP-Equiv=”IB_OnKey0x000d” content=”Javascript:setOkCodeEnter();”>

This code is OK for Intermec Browser but for iBrowse you have to replace ALL IB_OnKey by iBrowse_OnKey.

I dont know, why this has been changed and why the old syntax cannot be used anymore.

If you need html working with both locked down browsers, you can enter IB_OnKey and iBrowse_OnKey in parallel. The browser ignores what he does not recognize.

Bookmark It