> I'm not sure exactly what you're talking about here. What would be the
> purpose of writing an application that didn't take the scanned information
> and insert it into a text field? The scanner on a SPT-1500 can read a
> variety of bar code formats, and if you're looking for the right events,
> there's no problem with grabbing that scanned data. That's the whole
>point of the
> SPT isn't it?
> Also, I'm curious as to what the browser (I'm assuming on the PC) would
> possibly have to do with the SPT, and 'invoking' the scanner, which I assume
> to mean turning the laser on...?
> We must be talking about two different things here!
I don't think so; perhaps I wasn't clear. Mark's right (included message
below). This is exactly what I meant. An application, by itself, doesn't
know about scanning. You have to tell it to accept scan events (and enable
the scanner to generate scan events; this is what I meant by "invoking the
scanner"; sorry about the sloppy language). A given web browser -- on the
*Palm* side -- needs to (a) turn on the scanner and the scan decoder
hardware, and (b) accept scan events generated by that hardware. This has
nothing to do with the PC.
Does that clear anything up?
Regards,
Ben Flaumenhaft.
>What Ben meant (I think) was that the way the SPT 1500's scanner works is
>that an app has to enable the scanner and setup the field to accept input
>from the scanner. Then, when the user pushes the scanner buttons the laser
>is emitted and a barcode is read, decoded and sent off to the field in the
>app.
>
>The purpose of the hack is that apps that weren't written for the 1500
>don't know how to enable the barcode reader and to accept input from the
>barcode reader if one were to exist. The hack would allow existing
>application use the scanner without being rewritten to take advantage of
>the scanner.
>
>mark
>
