Can I use nodeset and path at the same time?

[woohyuk.park]

Hello Experts,

I want to use "nodeset" and "traffic path" function of NeXt UI at the same time.

However , these two function do not work at the same time.

How do I can use two functions at the same time?

Thanks,

woohyuk

[etiennegeorgy]

Hello woohyuk,

Have you found out if it's possible to use nodeset and path at the same time?

Currently I'm working on a similar problem and get the same error.

I'd like to draw a simple path over a topology with nodesets.

Thanks,

Etienne

[aaikepae]

Hi Etienne,

You can refer this demo : https://jsfiddle.net/nextsupport/t7gwpcxf/

Abu

[etiennegeorgy]

Hi Abu,

Thank you for your answer and the demo.

Is it somehow possible to draw a NodeSetPath only between two nodes? Or between a Node and a NodeSet?

My specific problem is, that I want to use single links for drawing a Path.

For example to use the "arrow" and "reverse" properties from "Topology.Path".

The picture below should hopefully explain what I mean

Thanks,

Etienne

[lindsayg]

Came across this same issue, you will need to adjust the Topology.NodeSetPath class, add the following where suitable.

                            // Fix 1-link bug
                            if (visibleNodesLength === 2) {
                                line = line.pad(padding, arrow ? padding + strokeWidth : padding);
                                d.push('M', line.start.x, line.start.y);
                                d.push('L', line.end.x, line.end.y);
                            ....
                            ....

[jamessmilleree]

It's understandable that you'd want to use both the "nodeset" and "traffic path" functions in NeXt UI simultaneously for a more comprehensive approach to your task. However, it seems you've encountered a limitation where these two functions don't work together seamlessly.

Here's my perspective:

Check Compatibility: Firstly, ensure that both the "nodeset" and "traffic path" functions are compatible with each other within the NeXt UI framework. Review the documentation or reach out to NeXt UI support to confirm this.

Thanks

[lindsayg]

Using NodeSetPath.

NodeSetPath's need to be created while NodeSet is expanded. With the code above, it fixes the 1-link bug. Also seems to require some modifications to BasePath class as it doesn't hide the NodeSetPath's arrow when a NodeSet is collapsed.

I tend to prefer the NodeSetPath, as it takes less to implement (just need Node Ids), and generally I just want line arrows to represent a direction. They don't necessarily need to be attached to individual links.

Could also just use Bezier curves class, I guess.