Replies: 5 comments 5 replies
-
For no.1 I agree, we can abstract the layout manager to accept |
Beta Was this translation helpful? Give feedback.
-
Try it make it work
Both resizing and positioning are layout |
Beta Was this translation helpful? Give feedback.
-
I would like to do the same, how can I make it compatible with Node environment at the same time? |
Beta Was this translation helpful? Give feedback.
-
These methods are missing in Canvas rotate() {}
calcOwnMatrix() {
return [1, 0, 0, 1, 0, 0];
}
getRelativeCenterPoint() {
return new Point(0, 0);
}
setPositionByOrigin() {}
setCoords() {} |
Beta Was this translation helpful? Give feedback.
-
I do not think a Layoutmanager for the canvas is needed. |
Beta Was this translation helpful? Give feedback.
-
Original Discussion #9558, some thoughts on the new features of LayoutManager.
about 1:
I think all elements that have container capabilities should support layout capabilities.
Better structure or naming?
I was implementing something about what's in #9558 and realized that the formLayout dispatched getLayoutResult and its return type was confusing me.
At first I thought I needed to calculate the new position of each element. I should be applying the new position within each element.
I further discovered the
LayoutStrategy
capability, which I instinctively thought was what I needed, but once again I was wrong, and it still only returned one result.In my understanding, in this feature of layout, when every time an element changes, I should go and calculate a new position.
Beta Was this translation helpful? Give feedback.
All reactions