DataWedge Configuration 4 - 31
While DataWedge is running it receives a notification from the system that a datawedge.db file is placed into
the /enterprise/device/settings/datawedge/autoimport folder. When this occurs, DataWedge imports this new
configuration, replacing the existing one and delete the datawedge.db file. DataWedge begins using the
imported configuration immediately.
Programming Notes
Overriding Trigger Key in an Application
To override the trigger key in an application, create a profile for the application that disables the Barcode input.
In the application, use standard APIs, such as onKeyDown() to listen for the KEYCODE_BUTTON_L1 and
KEYCODE_BUTTON_R1 presses.
Capture Data and Taking a Photo in the Same Application
To be able to capture bar code data and take a photo in the same application:
Create a Datawedge profile pertaining to the picture taking Activity in your application that disables scanning
and use standard Android SDK APIs to control the Camera.
The default Datawedge profile takes care of the scanning in the application. You might want to create another
DataWedge profile that caters to any specific scanning needs, associated to your Application's Activity
pertaining to scanning.
Disable DataWedge on MC40 and Mass Deploy
To disable DataWedge and deploy onto multiple MC40 devices:
1. Touch > DataWedge > > Settings.
2. Unselect the DataWedge enabled check box.
3. Export the DataWedge configuration. See Export Configuration File on page 4-30 for instructions.
See Configuration File Management on page 4-30 for instructions for using the auto import feature.
NOTE It is strongly recommended that the user exits DataWedge before remotely deploying any configuration. It
is required that the dataWedge.db file permissions are set to 666.
To Next Page
Loading...
Need help?
General
