-
Notifications
You must be signed in to change notification settings - Fork 10
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
Boundary functionality removed? #5
Comments
Hiya, looks like that got missed out, I think because the original conversion didn't have it in, so has never been part of it to try and get working. |
Thanks for letting me know. https://github.com/AliasIO/Raphael.FreeTransform This version has it build in, but i prefer your fork, because of the awkward rotation/resize handle on the original version. Also great job so far on your plugin! |
Just out if interest, what's the main desire for the boundary....is it to keep the element with a limited area, or a dragger, or the center of an element within an area, or something else ? |
The goal is to restrict the element to a container on a dragevent. So basically making sure that rectangle A (element) stays within the borders of rectangle B (container) |
I think this is probably more complicated to do a decent solution than it sounds... For example, suppose it's a rotated set of rects. Then we scale it by 2...what do we want to happen. It will be 'over' the edge. You can possibly hook into the callback that ft takes, and check for the apply/drag events, and do some tests on that, and try and figure a case that works for you. |
I noticed that the Boundary attribute is missing in your version, did you completely remove the functionality or did you replace it with and am I looking over it?
The text was updated successfully, but these errors were encountered: