We’ve recently had a number of projects that required the use of a serial devices in desktop applications. In all cases the clients said the devices are, “easy to use,” since they act just like a keyboard. If our experience is typical then I’d hazard a guess that many Xojo developers are frustrated with them.
Several projects required the use of barcode scanner. Having a barcode scanner work as a keyboard makes sense, I guess. It means that it can work with literally any application, anywhere, any time. All it needs is focus on a text field and whatever the scanner sees it puts into the control.
In another project we had an ultrasonic sensor that would take the application out of idle mode and present the user with purchasing information. Again, it acted just like a keyboard which means it works with any application as long as you had focus in a text field.
If you happen to know WHEN this information is going to come in it’s not so bad as you can plan for it. Putting the focus in a field and waiting for information is easy. It’s not so easy when that information could come at any time. Of course all of our applications had data that could come in at any time and we had to be prepared to act on it immediately.
If you rely on a TextField or TextArea getting this information the rest of your interface can really suffer. It means that when your barcode/sensor field loses focus you have to get it back (or you lose information). Do you do this right away or wait a few seconds? And if you have a complex user interface how do you deal with tabbing between controls, or even simple things like a user changing a checkbox because the focus is lost on your TextField? It can be a nightmare to try and figure out and get right. The differences between Mac and Windows and Linux can be frustrating!
The answer that we ended up implementing was putting the barcode readers into serial mode. I’ve not run into a barcode scanner yet that couldn’t be used in serial mode. Every scanner has a gazillion different modes and properties (all set via barcode of course) and one of them is to make it appear as a serial device to the computer. On Windows this is a COM port and on the Macintosh they tend to show up as a USB Modem. If I had to guess I’d say it’s harder getting barcode readers that are Mac and Linux compatible.
Once it’s in serial mode it’s almost trivial to create a class that monitors the serial port and reads the data WITHOUT needing the focus in a TextField. The class then distributes the data to the objects that can consume the data. What I do is have the window or objects register itself with the class and then when the data comes in the class sends it to all registered objects. Each of the objects has an Interface with a simple HandleBarcode method. This is known as the Observer Pattern and there’s an example that ships with Xojo.
My ultrasonic sensor wasn’t so easy to overcome as it couldn’t be put into serial mode. However, it did come with a Windows-only SDK (thankfully it was a Windows only project) and with a little help with Declares we were able to get it working so we could tell if someone had walked up to the device and when they had walked away. I’m not sure what we would have done if it had been a Mac or Linux project.
Serial Devices are relatively easy to work with in Xojo (as long as they show up in the serial list). Having to deal with devices that act as keyboards not so much. I’d highly recommend trying to get them to work as serial devices and save yourself a ton of grief.
What’s been your experience with serial devices in Xojo?