Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set_node_position_bypass does not support z_locations #145

Open
matthiaskoenig opened this issue Oct 28, 2024 · 4 comments
Open

set_node_position_bypass does not support z_locations #145

matthiaskoenig opened this issue Oct 28, 2024 · 4 comments

Comments

@matthiaskoenig
Copy link

Currently, the set_node_position_bypass does not support z_locations, only x and y.
It should be possible to set the z-index (z-position) for fine grained control over the z-order of nodes and the resulting overlap of nodes and edges.

See example image attached. Overlap order should be identical for the different node sets.
image

I will provide a pull request for that. Just opening the issue so it is documented.

@bdemchak
Copy link
Collaborator

Hi, Matthias --

I think this use case came up a long time ago, and I don't remember why it was de-prioritized. Maybe @AlexanderPico does??

In any case, you should be able to set the Z coordinate by calling set_node_property_bypass() directly and passing the 'NODE_Z_LOCATION' property.

Does this help??

@AlexanderPico
Copy link
Member

I presume it's because 99.999% of users only think about x,y and including z would confuse them or at least add to the cognitive load for using the method.

@AlexanderPico
Copy link
Member

You are definitely in the advanced user category.... like top 0.0001% :) So, you can use the advanced methods like set_node_property_bypass()

@AlexanderPico
Copy link
Member

(cool use case, btw!)

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

No branches or pull requests

3 participants