The simplest solution for you may be to create different DataWedge profiles and associate each with an activity in your application. By configuring the respective DW profiles appropriately e.g. one having SimulScan input enabled, another having Barcode input enabled with datamatrix etc you may avoid coding a lot of the logic into your application. Under the covers, the ProfileManager is just creating these profiles so hopefully you are already half way there. By letting DataWedge handle the logic of switching between the two input types (Barcode & SS) it should not block your app, be more stable & hopefully you would see a performance improvement.
If you wanted to go down the code route you could use the SimulScan & Barcode API and share the instance across your different activities and this thread provides some suggestions on that: Best practice to use the scanner across multiple activities . I am reasonably certain that you would not be able to pre-enable both SimulScan and the Barcode API however as they depend on the same subsystem (and possibly the same physical hardware)
thanks for your valuable input and happy new year.
In the meantime I played around with the DataWedge Demo application and the KitchenSinkApp.
Also I modified the KitchenSinkApp and tried to scan a multi structured document which we created with the SimulScan Template Builder.
I never achieved to forward the user to the camera and confirmation screen (see screenshots), which we get if we use the SimulScanManager like this:
Is my understanding right that DataWedge cannot provide this interface like the SimulScanManager?
Accessing SimulScan through DataWedge should work and present a confirmation screen, I am not sure why it would not be doing so in your case. A couple of things to check would be whether you have the template in the correct directory and have activated it as described in this link: SimulScan Setup - Zebra Technologies Techdocs . I also considered perhaps you required a license to do this (SimulScan Licensing - Zebra Technologies Techdocs ) but the licensing requirements for the SimulScan Manager and Datawedge should be the same.
You may find Peter's recent blog an interesting read (EMDK for Android in Multi-Activity App ), it is concerned solely with the barcode scanner but you may be able to adapt the technique to also work with the SimulScan manager.