We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'd like to set anchors like so:
NW, NE, SE, SW = scale E, W = resize N, S = hidden
What I've tried...
{ keepRatio: true, renderDirections: ['nw', 'ne', 'se', 'sw'], resizable: { resizable: true, renderDirections: ['e', 'w'], }, draggable: true, edgeDraggable: true, rotatable: true, scalable: true, };
Ideal config would be...
{ keepRatio: true, resizable: { edge: ['e', 'w'], renderDirections: ['e', 'w'], }, scaleable: { edge: [], renderDirections: ['nw', 'ne', 'se', 'sw'], } draggable: { edge: ['n', 's'], renderDirections: ['n', 's'], } };
I'm getting the feeling that these config isn't supported? Is that right?
The text was updated successfully, but these errors were encountered:
@pclancysc
okay. I'll add this feature in scalable.
Sorry, something went wrong.
feat: use edge at the same tiem #706
c273703
lit-moveable
moveable
preact-moveable
react-compat-moveable
react-moveable
svelte-moveable
vue-moveable
vue3-moveable
ngx-moveable
moveable's new version is released.
See https://daybrush.com/moveable/storybook2/?path=/story/advanced-resizable--using-edges-and-controls-with-draggable-resizable-and-scalable
triggerAblesSimultaneously={true} resizable={{ edge: ["e", "w"], renderDirections: ["e", "w"], }} scalable={{ edge: [], renderDirections: ["nw", "ne", "se", "sw"], }} draggable={true} edgeDraggable={["n", "s"]}
No branches or pull requests
Environments
Description
I'd like to set anchors like so:
NW, NE, SE, SW = scale
E, W = resize
N, S = hidden
What I've tried...
Ideal config would be...
I'm getting the feeling that these config isn't supported? Is that right?
The text was updated successfully, but these errors were encountered: