You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi guys,
in a previous issue you had the following idea :
In future we could support type="barcode-ean-128", or type="qrcode", or type="line", etc.. but they are optional features.
Is the barcode printing in comment lines still on the table for implementation?
It has a 'real-life'use for a lot of purposes.
P.S.
Can you please add an example for the /rawcommand as I tried to eventually use that for printing the barcode, but most protocols will want the Bon to be opened first so I think it may not be possible to use it that way unless the whole receipt is not being printed 'per-line'via rawcommands or I'm mistaken about that?
The text was updated successfully, but these errors were encountered:
Hello guys and thanks for the good work done.
IMO it would be great to add a command to allow printing a non-fiscal receipt along with the 1D barcode (as QR code currently is not supported by some if not most printers and has to be printed as an image). Tons of useful applications for it. I hope currently it's achievable by using raw command (haven't tested this yet), but would be a good feature.
Also, how about printing an invoice? So far seems there's no command for this :(
Hi guys,
in a previous issue you had the following idea :
In future we could support type="barcode-ean-128", or type="qrcode", or type="line", etc.. but they are optional features.
Is the barcode printing in comment lines still on the table for implementation?
It has a 'real-life'use for a lot of purposes.
P.S.
Can you please add an example for the /rawcommand as I tried to eventually use that for printing the barcode, but most protocols will want the Bon to be opened first so I think it may not be possible to use it that way unless the whole receipt is not being printed 'per-line'via rawcommands or I'm mistaken about that?
The text was updated successfully, but these errors were encountered: