What happened to klipper that it is no longer able to generate barcodes or other types of scannable codes like Aztec. It only gives the option for qr now. Do I need to install a dependency?
Hi, I’m sorry that question is rather too vague in its present form. ![]()
When I searched for klipper in the repos and AUR, I found 3D-printer firmware and a couple of related utilities, so it will certainly help if you can explain what this software is, where you got it from (and how you installed it), as well as what you are using it for.
It may of course also be benificial for you to provide some System Information:
inxi -zv8
Note that the output produced by this command is privacy-filtered.
Please also remember to use proper code formatting as this makes it much easier to read on the Forum:
[Mini How-To] format code or command output
Select and copy all the text in the Terminal window (minus the prompt, if you are using zsh).
Then paste the output in between two lines containing three backticks
```
or three tildes
~~~
Or:
Copy & paste, then highlight the pasted text and click the </> button at the top of the reply window (easier for smaller outputs).
Cheers! ![]()
Looks like they’ve removed the ability to generate other types of barcode.
You’d have to ask them to put it back in, or use another utility to create other types of barcode.
For what it’s worth.
I fiddled with the following a number of years ago. It does (did?) many types of codes, except QR (I think):
https://pypi.org/project/python-barcode/
Docs:
You can output to image (via PIL) or to SVG. The latter so you can enhance it in, e.g. Inkscape after, plus you will get a much better result.
It was just for a general interest I tried it, to see what could be done. Haven’t used it since then so I have no longer any idea of its status.
This is the merge request with the explanation and discussion:
It can be nice to have fancy qr codes etc though.
Seems very much like a “I don’t use this so no one should” merge request, there’s probably “no strong reason” to remove it either.
I did spot a few people mentioning issues with large clipboard contents when I was looking into this earlier.
![]()