Skip to content
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

lw450tt.ppd cupsManualCopies settings #10

Open
jck000 opened this issue Oct 30, 2020 · 3 comments
Open

lw450tt.ppd cupsManualCopies settings #10

jck000 opened this issue Oct 30, 2020 · 3 comments

Comments

@jck000
Copy link

jck000 commented Oct 30, 2020

I used a ppd file from the original Dymo tar file which has *cupsManualCopies = True. However, all of the files here have that parameter value set to False. Having it set to False will not honor '-n XXX' from the lp command. When changed to True, '-n XXX' will correctly produce the number of copies specified.

On my system I have a LabelWrite 450 and a LabelWriter 450 TwinTurbo and have tested the ppd
files with *cupsManualCopies = True.

I suggest a change to all ppd files:

*cupsManualCopies = True

Thanks,
Jack

@Kyle-Falconer
Copy link
Owner

That's an interesting find. Can you provide a link for this tar file?

@jck000
Copy link
Author

jck000 commented Oct 30, 2020

Let me be clear, the original ppd file, I don't think I edited it at all and I haven't compared all of the ppds with your fork. I've got the original installed on Ubuntu and Centos. I've gone ahead and installed that on a Raspberry PI, but as you probably know anything from Dymo is old and only supports intel versions of executables. I used your fork to deploy to a Raspberry PI especially for the LW450TT. On the original it would not allow me to switch slots. You fork has no problems with that. The -n option is the only issue I ran into and I did a simple comparison and that's what I found. Trivial. I wanted to share that with you.

Here is the link:

https://www.dymo.com/en-US/dymo-label-sdk-cups-linux-p

Thanks,
Jack

@Kyle-Falconer
Copy link
Owner

Ok, great. I thought that's what you meant. I'll take a look at it and make the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants