I had a funny thing happen when testing a barcode screening application this week.
Long story short, it turned out that I had inadvertently added the VID/PID for not one but both of my wireless keyboards (my travel one and my “home” one) at some point, with the result being that every time I struck a carriage return, Tulip Player would detect that as barcode device input.
This probably happened because I was having trouble figureing out which USB devices were which (now my device names for my actual barcode scanners have the VID/PID listed, and I’ve saved them via screenshot and in a OneNote table, just in case).
But have to I wonder if there is a practical application to this mistake.
Thoughts?
Hi @jmlowden
How sure are you that this has to do something with adding your Keyboard anywhere?
This is usual behavior and in most cases, there is no need to add any barcode scanners in the player.
Most Barcode Scanners behave as a keyboard. When you set them to suffix a CR it will be detected as Barcode Scanner by Tulip.
This results in any Keyboard getting detected as a Barcode Scanner, when you have not selected any text input and you type enter fast enough after typing anything.
There is no additional setting needed, but that also is no issue usually…
The Practical Application to this behavior in know, is that you can test Barcode Triggers also, when you have no scanner by hand 
1 Like
Yes, when I removed the custom barcode scanner connections corresponding to my two bluetooth keyboards, the behavior ceased.
To be clear, the unexpected behavior observed was that my normal typing using these bluetooth keyborards (but not the laptop keyboard) would be percieved as barcode device output by Tulip Player upon striking the enter key.
I haven’t been able to reproduce this without those Custom Barcode Scanner connections, no matter how fast I type/enter, but perhaps that is because I am on LTS 8.2?
