Node position changes on `setItemState(... ,false)`
See original GitHub issue- [ V ] I have searched the issues of this repository and believe that this is not a duplicate.
Reproduction link
Steps to reproduce
Hover and leave nodes to see the position of node border change (moves halfway right and down) while label stays it it’s initial position.
It happens when graph.setItemState(... , ... , false)
(or graph.clearItemStates()
) is applied.
Environment | Info |
---|---|
g6 | 4.0.2 |
System | Windows 10 |
Browser | Версия 87.0.4280.66 |
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
How to set the new Node position always be Under the ...
What I want to achieve is that every time I add nodes I want their positions to be rendered on the previous node...
Read more >Configuration - Ant Design Charts
The anchorPoint of a node is the link point where the related edges link to. In other words, it is the intersection of...
Read more >CTreeCtrl Class | Microsoft Learn
Returns the current position of the cursor related to the CTreeCtrl object. CTreeCtrl::InsertItem, Inserts a new item in a tree view control.
Read more >wxTreeCtrl Class Reference - wxWidgets
Adds the root node to the tree, returning the new item. More. ... virtual void, EndEditLabel (const wxTreeItemId &item, bool discardChanges=false).
Read more >SwfTreeView Object - ADM Help Centers
MouseMove, Moves the mouse pointer to the designated position over the ... The full path of the node to activate in the tree-view...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Fixed by 4.0.3.
It will be fixed in 4.0.3 soon.