Upgrade Guide for Anyline 44.0.0
We have completed a major update to the Anyline classes in version 43. If you were coming from a previous Anyline version, it is important to go over some of the more significant changes in this page. For more detailed information about the classes, please head over to the API documentation API documentation.
Updating the JSON configuration
Here’s a direct comparison of the same JSON configuration in the old vs. new style:
Old JSON |
New JSON |
|
|
1 | camera is now called cameraConfig (see 7.) |
2 | flash is now called flashConfig (see 8.) |
3 | viewPlugin is now called viewPluginConfig (see 9.) |
4 | plugin is now called pluginConfig and does not include a plugin anymore, instead it includes the XXXconfig (in this case meterConfig ) |
5 | scanFeedback is now called scanFeedbackConfig (see 11.) |
6 | cancelOnResult is not part of the viewPlugin anymore, instead it is part of the pluginConfig (see 10.) |
Updating the Scanning Implementation
Here’s a direct comparison of how the scanning implementation changed:
Old Implementation |
New Implementation |
|
|
1 | You don’t need to implement any more callback interfaces |
2 | The type of ScanView.ScanViewPlugin is now a ViewPluginBase which can either be a ViewPluginComposite or a ScanViewPlugin - in this case, it’s the second one. (See 5.) |
3 | There is no more result listener - instead, directly access the ScanPlugin and register to the respective event - in this case: ResultReceived (see 6.) |
4 | There is no more implementation of an interface, instead provide your own implementation that shall be called once an event is received (see 7.) |
Have a look at the Scanning Capabilities section for more specific implementation details.
Any questions? Reach out to us via [email protected]!