You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2024. It is now read-only.
Currently, if you have an object positioned so that it is not aligned perfectly with the grid (e.g. positioned using the arrow keys or as a result of snapping to something else not on the grid), resizing with the vertical handles will also resize the shape horizontally, snapping it to the nearest grid line.
This is definitely unexpected behaviour, since the user is explicitly trying to resize in a single direction.
From a brief play around, it seems this is caused by the GeometryEditor.handleMouseMove function calling Util.gridNormalize(...) on the newX (and newX2) variables without actually checking if the resize should be altering the width at all. (this is all in app/editor/geometryEditor.js, around line 400)
This should be a simple fix, so I'll try to get a PR up when I have time in the next few days.
The text was updated successfully, but these errors were encountered:
Currently, if you have an object positioned so that it is not aligned perfectly with the grid (e.g. positioned using the arrow keys or as a result of snapping to something else not on the grid), resizing with the vertical handles will also resize the shape horizontally, snapping it to the nearest grid line.
This is definitely unexpected behaviour, since the user is explicitly trying to resize in a single direction.
From a brief play around, it seems this is caused by the
GeometryEditor.handleMouseMove
function callingUtil.gridNormalize(...)
on thenewX
(andnewX2
) variables without actually checking if the resize should be altering the width at all. (this is all in app/editor/geometryEditor.js, around line 400)This should be a simple fix, so I'll try to get a PR up when I have time in the next few days.
The text was updated successfully, but these errors were encountered: