Alexander Horner
Alexander Horner
I think I'm running into a similar issue with dynamically sized nodes, probably due to the new `node.measured` stuff. I'll see if I can reproduce it. The migration from v11...
My issue seems to arise from measured not being calculated correctly during the initial render. I rely heavily on custom edge logic that depends on width and height. It would...
I was working on a minimal reproduction, but unfortunately, I can't spend more time on this, at least for now. My custom edge tries to find the closest edge and...
The other problem is happening here: ```ts onNodesChange: (changes) => { const nodes = get().nodes set({ nodes: applyNodeChanges(changes, nodes) as TableNode[], }) } ``` ``` index.mjs:582 Uncaught TypeError: Cannot assign...
Fixed the edge calculations by also applying the same subscribe "hack" ```ts const targetDimensions = useStore(reactFlowStore, s => s.nodeLookup.get(source)?.measured) const sourceDimensions = useStore(reactFlowStore, s => s.nodeLookup.get(target)?.measured) ``` Now the custom...
> The other problem is happening here: > > ```ts > onNodesChange: (changes) => { > const nodes = get().nodes > set({ > nodes: applyNodeChanges(changes, nodes) as TableNode[], > })...
Yes it was auto freeze, took a long time to figure out... Sorry for not posting an update here, I thought I did. Why is `const { nodes } =...
Native context menus usually disappear on scroll or dragging. That's how I did it with my context menu and it feels pretty good. If you want it to move with...
Yea 0.11.4 doesn't fix the issue. Have to downgrade to 0.11.2
> In the end, I just added `fonts: { defaults: { weights: [400, 500, 600, 700] } }`. > It's just weird that it clain to be "zero-config", I think...