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

Scale X Y Z UI value/ boxes seem to be incorrectly wired or placed with respect to each other. #7799

Closed
twobob opened this issue May 21, 2020 · 6 comments
Labels
Status: Duplicate Duplicate of another issue. Type: Bug The code does not produce the intended behavior.

Comments

@twobob
Copy link

twobob commented May 21, 2020

Application version
4.6.1

Platform
Windows 10

Printer
Creality CR10

Reproduction steps

  1. I selected an object and chose SCALE
  2. I dragged to tool handle in the Z axis to increase the value and observed the %age value being updated in another column.

Screenshot(s)
image

Actual results
The Y axis %age increased rather than the Z axis %age value

Expected results
The relevant axis %age changing relative to the manipulated intended measurement

Additional information
It results in wacky resizes when clicking around in the zoom boxes after resizing something absolutely.

@twobob twobob added the Type: Bug The code does not produce the intended behavior. label May 21, 2020
@ssavickiy
Copy link

I also encountered this error
Безымянный

@64Florian
Copy link

look like it's the old bug #4136

@twobob
Copy link
Author

twobob commented May 22, 2020

Ah thanks. I did search trying to find it. so saving the object AS AN OBJ, AFTER rotating it to the desired location, and then closing and reopening the object as an obj would fix it then? (temporarily anyway, for that model)??

I'm reading the notes on #4136 and ghostkeeper does seem to imply there is a "working" state that can be achieved somehow... thanks for the info

@fieldOfView
Copy link
Collaborator

As long as the model is not rotated in Cura, the boxes will be "correctly wired".

@twobob
Copy link
Author

twobob commented May 22, 2020

I see, so it's some kind of projection issue. Fine. Thus my hack should work for all cases. Good to know

@Ghostkeeper
Copy link
Collaborator

Yeah, it's a well known but decently difficult bug.

Closing this as duplicate of #4136, #3625, #4309, #4386, #5221, #5189, #5310, #5462, #5599, #5602, #5603, #5872, #5916, #5965, #6148, #6150, #6238, #6370, #6619, #6770, #6829, #6890, #6971, #7102, #7142, #7237, #7388, #7446, #7448, #7582, #7638, #7703, #7768 and #7778. Yup, it's bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Duplicate Duplicate of another issue. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

5 participants