You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Clusters have wrong position on the screen.
To Reproduce
Steps to reproduce the behavior:
Use clusters in the latest versions.
You will see that clusters have wrong position (translate / transform properties) and depending how many nodes are in a cluster - it will be going worse and worse.
It's a simple issue with the latest code.
Expected behavior
Clusters have proper width to wrap all the nodes inside.
Describe the bug
Clusters have wrong position on the screen.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Clusters have proper width to wrap all the nodes inside.
Screenshots
![Screenshot 2024-01-04 at 14 34 42](https://private-user-images.githubusercontent.com/9199537/294193825-dfeeb953-e038-4b35-9268-fc2850825040.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU2NjA5NTYsIm5iZiI6MTcyNTY2MDY1NiwicGF0aCI6Ii85MTk5NTM3LzI5NDE5MzgyNS1kZmVlYjk1My1lMDM4LTRiMzUtOTI2OC1mYzI4NTA4MjUwNDAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwNiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDZUMjIxMDU2WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MGFkMDk0YTk1YTU0ZjZkNzg0NmVkN2U3Yzk5YzYzZmU4OTAyNWRkNzM1NDY1ZWJmMjU0NjcxZDA5YTM4YzJjNyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.v1tK2dpFK_W71WAE7H_6orWCKXnitYgyLQULUMAsLlA)
Demo
https://stackblitz.com/edit/angular-kfufe3?file=src%2Fapp%2Fapp.component.ts
ngx-graph version
8.2.3 - only here, because it has been introduced in this PR: #528
Additional context
The issue is a simple wrong calculation here done for clusters: https://github.com/swimlane/ngx-graph/pull/528/files#diff-e500ec710d86f32d459d34a450582fe79dcb541617240d848fa6319a389fa46aR454
Please take a look that dividing by 2 is now done twice which causes the issue. The flag has been handled wrongly here.
The text was updated successfully, but these errors were encountered: