Support Forums - View Thread

View Thread

The following is the text of the current message along with any replies.

Messages 1 to 3 of 3 total

Mon, Jun 20 2016 4:48 AM	Permanent Link
Pasquale Web Pos srl	Hi I am having a bar in chrome code reading problem with some DATALOGIC Heron D130 readers . The gun acquires the queue but the field is not filled . Obviously trying to iexplorer works fine . I can not understand it depends on the code generated by us or chrome is a problem with the specific bar code reader .
Mon, Jun 20 2016 5:05 AM	Permanent Link
Matthew Jones	Pasquale wrote: > The gun acquires the queue but the field is not filled . Pardon? Is this a reader which is using USB keyboard emulation? That should "just work" regardless. What may be an issue is if you have any pre- or post- code characters. On mine, for example, I think I have something like F8 programmed, and an Enter at the end. F8 was chosen because it is inert in most software, but it meant that the software I wrote could intercept it, pop up a different dialog, interpret the code according to the text that came in, and put it in the proper field on the main form. (This was all Windows desktop.) Perhaps something like that is affecting Chrome, which interprets the key itself? (One thing I did was add a field in the tool to tell me exactly the key strokes that were coming in, so that I could check what was up. I also included setup PDFs for our supported scanners so that anyone could beep, beep, beep and know it was properly configured.) -- Matthew Jones
Mon, Jun 20 2016 5:51 AM	Permanent Link
Pasquale Web Pos srl	solved . just download the programming codes of the bar code and then also works with chrome "Matthew Jones" wrote: Pasquale wrote: > The gun acquires the queue but the field is not filled . Pardon? Is this a reader which is using USB keyboard emulation? That should "just work" regardless. What may be an issue is if you have any pre- or post- code characters. On mine, for example, I think I have something like F8 programmed, and an Enter at the end. F8 was chosen because it is inert in most software, but it meant that the software I wrote could intercept it, pop up a different dialog, interpret the code according to the text that came in, and put it in the proper field on the main form. (This was all Windows desktop.) Perhaps something like that is affecting Chrome, which interprets the key itself? (One thing I did was add a field in the tool to tell me exactly the key strokes that were coming in, so that I could check what was up. I also included setup PDFs for our supported scanners so that anyone could beep, beep, beep and know it was properly configured.) -- Matthew Jones