fixes a problem when Cura starts with a single extruder printer but the
user then choose a multiextruder printer - CURA-4386
Also added a quality definition in UM3E extruder with the ids of the UM3
extruders, so that the profiles for UM3 are also valid for UM3E and viceversa - CURA-4389
All are related issues with profiles and multiextruder printers
Modified version of the Prusa i3's definition. While the i3 values work,
the print time estimations were horribly imprecise (often the print
takes 2x to 3x as long as Cura estimated). Therefore, I inspected the
problem, and found a Reddit thread [1] about it. Instead of hacking my
own installation, I just wrote a defition including the correct
acceleration/jerk values that work with my firmware (custom build of
Marlin based on https://github.com/JimBrown/MarlinTarantula/).
There's downsides however. I don't know how it performs with the stock
firmware (although I doubt there'd be many differences). Furthermore,
the `jerk_xy` is set to 4 in my definition, but that's only true for
the `x`value,the Marlin firmware has a `y` jerk value of 7. That leads
to minor differences in the printing time (e.g., just finished a print
which Cura estimated with 13h 30m, but it took 12h 50m).
Feedback from stock firmware users is therefore highly welcome. Also, if
someone could provide information about the jerk values and help
improving those inaccuracies, that'd be awesome.
[1] https://www.reddit.com/r/3Dprinting/comments/5wz0xs/
Any pixel size specified in QML should not either use UM.Theme.getSize(), or use screenScaleFactor to make sure the pixel size is as intended on OSX, Windows and Linux regardless of display DPI.
Contributes to CURA-4376
Any pixel size specified in QML should not either use UM.Theme.getSize(), or use screenScaleFactor to make sure the pixel size is as intended on OSX, Windows and Linux regardless of display DPI.
Contributes to CURA-4376
Apparently it's not allowed to be in there. By being commented out I hope that a future developer won't make the same mistake and add it there to be editable in the interface.
Apparently it's not allowed to be in there. By being commented out I hope that a future developer won't make the same mistake and add it there to be editable in the interface.
