rounded numbers on transform
It would be good if there would be a smart number rounding when ever transforms happen. So when moving an object 1,0315242 m. It could be automatically rounded to like n-digets behind the main number, so you get 1,03 m (For 2) and 1,032 (For 3). Rotation and Scale could be set to like 0.5 °. This is different to snapping, because it would affect all transforms as standard, so people don't run into super long numbers all the time.
6 Comments
Actually this is not uncommon in 3d and 2d Software, and it has zero affect to snapping. It’s just minor precision snap for very small number that only happens on screen scale transform. For example you move on 1 km scale a house, you would get like a 1 meter snap, that is about pixel on your screen. In other words, what’s the benefit if that house got moved 2.6712114 meters instead of 3 m on that scale? The user see only a 3 pixel move in both cases but got a lot better number that he can read
* @robert * But what you describe is jut Incremental snapping. Or not?
Also here already suggested values settings for increment snapping
* @robert * And such rounding will affect " snapping " precsion. If you want to move something and snap it to some vertex so you need to move for exactly 0.237 m. but you move by 0.01 incrementat you would not achieve this vertex. You will get 0.23 of 0.24 but not 0.237... Am I wrong?
* @robert * if you're working with scales that large and interacting with objects far enough away that it matters, you shouldn't epect any kind of precision, as that is a very imprecise way to work.
Here let me just slice this pizza with a hammer.. WHAT! why is my pizza so messy now, somebody make me a hammer with more precision so I can cut this pizza.
But with such feature snap precision will work wrong. Lot of things start working wrong.
could you explain how this would ever be beneficial?