KamoCRM

Drop in place — jump every member, no softPush on release

Fixkamo-internal
Ya
30 Aprili 2026, 03:47 UTC
Mwandishi
kamo
Ahadi ya
ad7043f

The drift on release was softPushCluster firing on the user-drop path. A mega-cluster's bounds extend in all directions from the anchor, so the PADDING-margin / off-edge check almost always tripped, and resolveCollisions animated the anchor away from where the user released — that was the "random direction" symptom. On release we now jump() every member of the cluster directly to its final seat (anchor + axial offset + center alignment) and jump() the anchor to the release point. No spring physics, no soft-push. The user picked the spot — we honor it. Soft-push still runs in reflowAllClusters / size-change flows where automatic relayout is appropriate; we just don't second-guess explicit user drops.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei