Disable "USB Printing" plugin by default and add option to enable it in Add Printer wizard #19655
Labels
Status: Triage
This ticket requires input from someone of the Cura team
Type: New Feature
Adding some entirely new functionality.
Is your feature request related to a problem?
Hiya! It's your Friendly Forum Assistant Moderator Who Doesn't Visit The GitHub Repo Much Slashee here.
There have been increasing numbers of people having trouble with models taking >15 minutes to load posting, and the solution always seems to be disabling the USB Printing plugin (and how many people find the solution and don't post about it... I don't have analytics so I can't tell you 🙂)
I think there's been another couple of issues which have had the same solution, but it's mostly the former.
I'm always quick to step in with the "USB printing is deprecated and no longer supported" spiel in most of these cases.
Sadly there's a lot of people who come to the forum with problems getting their printer to work over USB (or other problems and it comes up that they print over USB) so I know that there's still a seemingly not insignificant number of people who use it.
Describe the solution you'd like
I think the USB Printing plugin should be disabled by default, but add an option in the Add Printer (in the non-networked section) wizard saying "I'll be printing over USB" which enables the plugin.
Maybe store it a machine instance setting so you can change it from the Machine Settings dialog without having to re-add a printer (then if you wanted to get all fancy like, you could dynamically enable it if any installed machines have it enabled).
Describe alternatives you've considered
Affected users and/or printers
This would help prevent the "models take ages to load" problem and possibly other bugs for people who would never use USB printing anyway.
Might shave a fraction of a second off the loading time for most people, too... not as important, although I have seen people complaining about the loading time.
Additional information & file uploads
No response
The text was updated successfully, but these errors were encountered: