-
-
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
[Feature]: i think Group should support controlsVisibility as constructor second options ? #10298
Comments
new Group([],{
_controlsVisibility:{
tl: false,
tr: false,
bl: true,
br: true
},
}) |
thanks, Private attributes may be removed at any time. The style is not very good, right? |
It is recommended to use custom controllers rather than simply showing or hiding elements. import { controlsUtils, Group } from "fabric";
Group.createControls = function() {
const controls = controlsUtils.createObjectDefaultControls();
delete controls.tl; // If you don't need to
delete controls.tr; // If you don't need to
return { controls }
} |
the controlVisibility object is one of the oldest fabricJS feature and was never part of the options. |
The product needs to turn off the rotation function and does not support rotation @asturur |
|
Wouldn't you just then delete the rotation control from the control set? |
I did not use the fabric api directly, but packaged it as react-fabric.Therefore, it is inconvenient to move the underlying configuration |
CheckList
Description
currect is noly has
Current State
no
Additional Context
no
The text was updated successfully, but these errors were encountered: