Replies: 2 comments 4 replies
-
So my first question is, why do you need to change the group size? what is the need behind it? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After using
Group
a lot the need to control it's size has become the main thing I have against it.Setting
width
|height
is irrelevant after adding/removing an object because it recalculates it's dimensions with_calcBounds
.I find myself extending group all the time because of this.
This is bad and is inconsistent with the rest of the shapes.
It is tough to handle for someone starting to use fabric and for others as well. It is very internal on the one hand and very unintuitive on the other. I lost a good amount of hours understanding this.
Ideas:
resizeOnAddRemove
similar torenderOnAddRemove
. It can default to true so it won't be breaking. The problem is we need a prop for positioning as well I think because sometimes group does that to.onSelect
to determine if and how it should resize:addWithUpdate
,removeWithUpdate
:addWithUpdate(object, options: {resize:boolean, reposition:boolean})
@asturur @melchiar
Beta Was this translation helpful? Give feedback.
All reactions