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

[Bug]: Scaling event does not provide current scale values until next scaling operation #10246

Open
7 tasks done
khairulashraff opened this issue Nov 1, 2024 · 1 comment
Open
7 tasks done
Assignees

Comments

@khairulashraff
Copy link

khairulashraff commented Nov 1, 2024

CheckList

  • I agree to follow this project's Code of Conduct
  • I have read and followed the Contributing Guide
  • I have read and followed the Issue Tracker Guide
  • I have searched and referenced existing issues and discussions
  • I am filing a BUG report.
  • I have managed to reproduce the bug after upgrading to the latest version
  • I have created an accurate and minimal reproduction

Version

6.4.3

In What environments are you experiencing the problem?

Chrome

Node Version (if applicable)

None

Link To Reproduction

https://codesandbox.io/p/live/7312f88b-f683-475f-be4d-fcc74a1143b8

Steps To Reproduce

  1. Create a resizable Rect
  2. Listen to the Rect's scaling event.
  3. transform.scaleX and transform.scaleY value does not change throughout the scaling operation. The value is the same as the ones in transform.original.
  4. Stop scaling, and start scaling again. The value will now be the new scale and stay at that value throughout the scaling.

Expected Behavior

Return the most current scale value.

Actual Behavior

Returned the initial scale value as the scaling begins.

Error Message & Stack Trace

No response

@asturur
Copy link
Member

asturur commented Dec 4, 2024

I need to check what we do with the transform object. It may be is not intended to change and that you have to look at the target to know current scaling.
I need to look at the code because i don't remember

@asturur asturur self-assigned this Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants