Add proper support for binding clusters with sides optimization, not requiring synced layers #4
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently,
sidesoptimization inoptimize.pyandsides.pyassumes bindings across layers move together. This feature request proposes proper support for clusters, similar to how it is done innearestmode, to allow bindings across different layers to move independently even if originating in the same position.