Skip to content

Conversation

@Annonnymmousss
Copy link
Contributor

im still not getting how to create a segment in the first cmd + J only which is merging the layer but this issue is resolved..

Screen.Recording.2025-12-26.at.9.05.20.PM.mov

solving #3519

@Annonnymmousss
Copy link
Contributor Author

Screen.Recording.2025-12-26.at.9.08.30.PM.mov

there was this issue too.

Comment on lines +473 to +474
let start_point = resolve_id(layer1, start_point, 0);
let end_point = resolve_id(layer2, end_point, 1);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only ids in layer2 will change (since the layer1 will probably have no conflicts).

Furthermore it is possible that there is no conflict, in which case the original PointId must be used (like before this PR). You therefore need to check if there was some conflict by checking all of the point ids in the first path.

I don't care if this doesn't work for tables with several vector data, since I find them annoying.

@0HyperCube
Copy link
Contributor

@Annonnymmousss The issue in your video is the exact same as described in #3519 (the conflicting PointId is not updated so the wrong segment is created). However in my example, the incorrect segment wasn't visible (since it connected the point to itself).

@Annonnymmousss
Copy link
Contributor Author

working on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants