peterkogo
323e1b35c5
fixed evaluateAbsolutePosition for nested nodes
2024-11-04 10:41:52 +01:00
moklick
122f722742
chore(store): cleanup
2024-09-04 17:07:00 +02:00
peterkogo
535744efa1
typo
2024-08-20 12:46:00 +02:00
peterkogo
4a30f3a0fd
fixed node extent calculation and simplified calculateNodePosition
2024-08-20 12:42:57 +02:00
peterkogo
d9563505d8
fix node extent
2024-08-19 17:44:36 +02:00
moklick
62ba38cea9
chore(autoPanSpeed): cleanup
2024-07-04 18:03:22 +02:00
peterkogo
3f259e9662
variable autoPanSpeed
2024-07-04 16:33:45 +02:00
moklick
aa0e131162
refactor(react): init store with user nodeOrigin
2024-06-27 17:01:01 +02:00
moklick
f968ff42ca
chore(react): node origin cleanup
2024-06-26 15:26:22 +02:00
moklick
1a25a7da48
fix(store): calc handle pos
2024-06-24 14:38:45 +02:00
Moritz Klack and GitHub
67e29b6c25
Merge branch 'next' into absolute-origin
2024-06-24 12:57:24 +02:00
Luis Carlos and GitHub
abeb4086d3
fix: Correct parent node lookup in evaluateAbsolutePosition
...
### Summary
This PR fixes a bug in the `evaluateAbsolutePosition` function where the incorrect parent node was being retrieved from the `nodeLookup` in each iteration of the while loop.
### Changes
- Modified the line `const parent = nodeLookup.get(parentId);` to `const parent = nodeLookup.get(nextParentId);`.
### Reason
The original implementation used `parentId` to look up the parent node, which did not change within the loop. This resulted in the same parent node being used for each iteration, leading to incorrect calculations of the absolute position. By using `nextParentId`, we ensure that the correct parent node is retrieved and used in each iteration.
2024-06-05 09:29:48 -01:00
peterkogo
e81194d58a
Include origin directly in positionAbsolute of node
2024-05-22 15:38:08 +02:00
moklick
6c30686127
refactor(utils): cleanup getPositionWithOrigin
2024-04-18 09:17:51 +02:00
moklick
f242494b29
Merge branch 'next' into refactor/xy-drag-use-map
2024-04-16 18:00:32 +02:00
moklick
2102c17108
refactor(xydrag): use map for drag items
2024-04-16 17:09:51 +02:00
peterkogo
aad6de5359
simplified handleExpandParent, removed isParent, improved some functions
2024-04-16 16:54:38 +02:00
peterkogo
714d30b63f
fixed bug with expanding parent, made adjustments to evaluateNodePosition
2024-04-16 13:19:44 +02:00
moklick
8a56311e52
fix(intersection-helpers): use correct positions closes #4138
2024-04-15 13:18:57 +02:00
moklick
ea18e46a1a
refactor(nodes): rename computed to measured, add helpers
2024-04-03 14:54:24 +02:00
moklick
844d574c4f
refactor(react): separate user nodes and indernal nodes
2024-03-27 11:22:43 +01:00
Moritz Klack and GitHub
e5c667d068
Feat(nodes): add initialWidth and initialHeight ( #3953 )
...
* feat(react/svelte): add initialWidth/initialHeight closes #3793
* chore(packages): update changelogs
2024-02-27 15:21:35 +01:00
moklick
009fb42017
refactor(system): revise calcNextPosition
2024-01-24 13:04:44 +01:00
Peter
4accceb202
Added TSDocs for several public util functions & converted comments to TSDocs for internal functions
2023-12-05 12:12:21 +01:00
Peter
f5da8c6b75
TSDoc for getViewportForBounds
2023-12-04 18:06:01 +01:00
moklick
d812dbbe53
refactor(nodes): add computed attr for width/height and absolute position
2023-11-21 15:06:42 +01:00
moklick
90912a6c1a
reafactor(react/svelte): rename some util functions #3528
2023-11-13 10:45:06 +01:00
Peter
ada5b94673
feat(svelte) add fitViewOptions, closes #3440
2023-09-25 12:58:04 +02:00
moklick
9654eee4fb
fix(scroll): fast zoom issue on windows with ctrl
2023-08-14 16:13:12 +02:00
moklick
9dfec49ed5
chore(system): rename BaseNode/BaseEdge types to NodeBase/EdgeBase
2023-06-13 16:54:26 +02:00
moklick
51375cd482
chore(utils): another cleanup
2023-06-12 23:00:22 +02:00
peterkogo
moklick
Luis CarlosandGitHub
Peter