Hi,
On my app, when using my MC330M to scan an EAN, it outputs a single string using a single "change" event. My MC330M has DataWedge on version 6.7.39
Now I'm testing my app on a TC20 with DataWedge on version 7.0.4 and it breaks a feature because the output of an EAN scan is sent with multiple "change" events.
One "change" event for each characters.
So, on my MC330M, when scanning a EAN, I get a single "change" event with a string of 22 characters. See attached file ean_scan_output_MC330M.png
And on my TC20, when scanning the same EAN, I get 22 "change" events with a string from 1 to 22 characters. See attached file ean_scan_output_TC20.png
I can't find any documentation related to this, is there a configuration parameter to handle this behavior ?
Undocumented difference between DataWedge 6.7 and 7.0 |
2 Replies
up ^^
I'm using keystroke output.
I can confirm that on MC330M when the parameter keystroke_character_delay is set to 0, the output string is sent all at once.
And when that parameter is set to anything higher than 0, each characters are sent separately.
On my TC20, even if the parameter is set to 0, each characters are always sent separately.
I think this is a regression in version 7.0.
If keystroke_character_delay is set to 0, it makes more sens that the whole string is sent at once.
So my question is:
Is there a way to always send the whole string at once on my TC20 ?