Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Changing scale factors through "Object manipulation" sidebar doesn't always work #2510
Current version from master: 821ca0e
Operating system type + version
Linux (Debian unstable) / X11
I wasn't able to get a reproducible scenario for this, so I apologize for the incompleteness.
As you do this, the arrow gizmos appear on the object, as expected
Here I selected one object on the build plate, changed the X scale to 102 without touching the "link" button (which has been left on by default):
the object is not updated (no scaling gets applied to X) and neither were the linked YZ (my change was completely ignored), but you can see 102 in the input box...
However, if I deselect the object and select it again and attempt to change the X scale again my inputs are accepted.
I have no idea what actions need to be performed to put slic3r into this state. I generally prepare several build-plates and export the g-code in the same session, so there might be multiple things going on...
Mmmh, looks like. I generally have background processing on, so I never have to slice manually.
If I disable background processing and then slice the view is switched to preview. When switching back it's always reproducible.
So it might be related to view switching too (although just switching view without slicing doesn't trigger the issue)
The behavior changed.
Now the input field is reset to the previous value when focus is lost in some circumstances.
Notice how the first change in % from 100 to 102 is ignored, but if I try with a larger value it works (?).
I was having an issue in 2.0 that, if I tried to change (unlocked) scale factors by small precise amounts, the other two dimensions would change too. For instance, trying to set (x,y,z) = (101.5, 101.5, 99) I'd set X=101.5, Z=99, and Y would jump to 102.35 or some such, then when I set Y=101.5, X would drop to 100.3 or some such, repeat. Made it basically impossible to iterate on an HTPLA part I was heat treating.
I can only assume that issue is related to this one, because I can't find any other more accurate report, so I just came here to say: it's fixed in 2.1, thanks so much for all the work to do that!