![]() ![]() When you run EB v1.5 on our Android devices, DataWedge is completely disabled, even when EB is in the background… This locks the use of the scanner out for any other application that is in foreground while EB is in the background including DataWedge.īecause utilities like SwipeAssist, are linked to DataWedge: NO DataWedge -> NO SwipeAssist As always …“with great power comes great responsibility”: an application using the scanner object from the Barcode API, is required to release it when it’s going in the background (usually you do this handling in the onPause() callback in your native application).Įnteprise Browser implements its own Barcode API on top of the native EMDK Barcode API, however, due to the nature of the web application running inside EB, it does not release the scanner object. The current scanner framework implementation on our Android devices make available a single scanner object that provides full Scanner control. ![]() ![]() These utilities can be integrated, with some heavy lifting, and accepting some constraints. During Enterprise Browser hands-on lab, I got some enquiry about using other MobilityDNA utilities together with EB in particular how to integrate SwipeAssist and Simulscan. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |