-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SUGGEST] Customer Display Monitor (Secondary Screen) #68
Comments
It has the feature but only for Linux for now. No device to check on windows. |
Turns out the customer display implementation is not a real secondary monitor connected to the same way as the usual computer screens (HDMI, VGA, DP, etc) but rather a more traditional 2-line serial display (often called a customer pole display). Sorry for that. Sometimes in the future, someone (or me, if I have the courage to do so) with enough C++ and QML skills will probably implement this good feature anyway. |
Yes, it does not support the multiple display yet. That will need another window to other screen. And I am currently moving to flutter for the front end, so any user can easily implement their UI as they want. It should be easier to get flutter dev rather C++ dev here. |
Not to be confused with the current "Customer Display" which is a 2-line serial display that's already implemented.
Hello developers and contributors out there,
This app looks very promising for many startups and new businesses, as we don't ever have to worry about proprietary software and it's (sometimes) strict and expensive licensings.
However, I do have one suggestion: There exists a thing called Customer Display (the full-fledged one instead of the basic 2-line serial display), it's basically a secondary screen that allow customers to look at their purchase logs before a receipt was printed, and in some cases the cashier can put a QR code, so the customer can just scan the code instead of re-typing something from the receipt and/or the 2-line serial display.
If anyone interested with this feature is appreciated, thanks.
The text was updated successfully, but these errors were encountered: