-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
update(AligningGuidelines): Fix some bugs and add custom features. #10120
base: master
Are you sure you want to change the base?
update(AligningGuidelines): Fix some bugs and add custom features. #10120
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
2024-09-02.14.23.03.mov |
5e1acc1
to
326e756
Compare
326e756
to
9523d69
Compare
When the angle of the operated graphic is not 0, there is a bug with the 4-corner scaling alignment. I will solve it at noon tomorrow. |
fixed 2024-09-11.10.19.10.mov
|
In practical use, a common issue has been identified: when there are too many shapes, the problem of excessive reference line hits occurs because each shape is compared with the current shape. It is suggested to change the approach to count all points and use those points for judgment. (The same issue occurs in V5; if there are related requirements for V5, please refer to the modifications.) The following is a video comparison before and after the modifications. a.movb.mov |
I m sorry i didn't have time for this and i won't for a bit. |
Okay, I will take some time to write the test cases, while also adding the corresponding listener functions and disabling the relevant feature switches. |
@asturur |
Resolve the issue where when the user scales using scaleX, scaleY is not updated simultaneously. The same applies to scaleY.