|
@@ -239,7 +239,7 @@ for event in dev.read_loop():
|
|
|
```
|
|
```
|
|
|
|
|
|
|
|
Note that the `HID_NAME` is specific to the USB magstripe reader I had on hand.
|
|
Note that the `HID_NAME` is specific to the USB magstripe reader I had on hand.
|
|
|
-Multiple of the same could be attached and would need to be differentiated by thei `/dev/input/event*` endpoints.
|
|
|
|
|
|
|
+Multiple of the same could be attached and would need to be differentiated by the `/dev/input/event*` endpoints.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
@@ -249,7 +249,7 @@ Display
|
|
|
The passenger needs feedback so a display is required.
|
|
The passenger needs feedback so a display is required.
|
|
|
I think it's good practice to provide a mechanism for user interaction and high resolution display.
|
|
I think it's good practice to provide a mechanism for user interaction and high resolution display.
|
|
|
|
|
|
|
|
-The high resolution display can be used for fare media presenteation feedback.
|
|
|
|
|
|
|
+The high resolution display can be used for fare media presentation feedback.
|
|
|
For example, letting the rider see what the camera is seeing to better align a QR codes ticket.
|
|
For example, letting the rider see what the camera is seeing to better align a QR codes ticket.
|
|
|
|
|
|
|
|
The touch feedback can be used for complex fare media or for future options.
|
|
The touch feedback can be used for complex fare media or for future options.
|
