In the last studio update a tweak was made in how the input fields for rotation and movement snapping works. Inputting a zero into the movement snapping input field will now ‘untick’ the ‘Move’ checkbox and preserve the previous number from the input field, as mentioned in this post. This change however introduces a new problem. If you input the same number as was already inputted (while the checkbox is unticked), the checkbox will remain unticked.
This is a problem because a builder will sometimes want to switch between ‘no snapping’ and ‘snapping’ while working with a static grid size. So for example, a builder might want to switch between ‘no grid’ and a ‘one stud grid’. The usual workflow for this is to enter a ‘0’ when you want to disable the grid and then enter a ‘1’ when you want to go back to your one-stud grid. This no longer works, as demonstrated in the video below.
When I enter the number ‘1’, the checkbox remains unchecked. If I were to input any other number however, the checkbox will be ticked again. The same behavior can be seen when using the input field for rotation snapping. This behavior creates a poor user-experience when building and I expect that this was a small oversight that slipped through the cracks.
Expected behavior
When I input a non-zero number into the move or rotate increment input fields, I expect the corresponding ‘Move’ or ‘Rotate’ checkbox to become ticked, even when the number I entered is the same as was already inputted into the input field before.