SOLVED Using Path Selection

Hi,

I'm trying to get the path of edges that connects 2 points. For that task I normally use the Path selection tool from the select menu.

7758c646-cbb8-4209-9d09-232f86cb032b-image.png

However, when trying to reproduce this with python code, I'm struggling to input the 2 points into the tool to get the final edge selection.
I have tried with c4d.CallCommand(1021385) and also by checking tooledgeselection.h with no results (can't find any baseselect or vector as input for the points).

Is there any way to do this without implementing shortest path algorithms by hand?

Thanks,

Daniel

Hello @DGLopez,

Thank you for reaching out to us. Normally you would solve such things with SendModelingCommand, CallUVCommand or similar methods. The problem here is: Although the Path Selection tool might seem to be a member of the old or new modelling kernel, it actually is not.

It apparently was initially written for the UV-Editor, and still lives there, but then was repurposed as a more general tool. As a side-effect, the tool has fallen a bit off the wagon regarding being covered as either a modelling or uv command and has no command identifier which could be called from the public API. Since the tool has complex GUI inputs, you cannot just write to the tool container and then invoke CallCommand either, as you will then will be unable to define the start and end point of the path.

You will have to write such functionality yourself.

Thank you for your understanding,
Ferdinand

Hello @DGLopez,

Thank you for reaching out to us. Normally you would solve such things with SendModelingCommand, CallUVCommand or similar methods. The problem here is: Although the Path Selection tool might seem to be a member of the old or new modelling kernel, it actually is not.

It apparently was initially written for the UV-Editor, and still lives there, but then was repurposed as a more general tool. As a side-effect, the tool has fallen a bit off the wagon regarding being covered as either a modelling or uv command and has no command identifier which could be called from the public API. Since the tool has complex GUI inputs, you cannot just write to the tool container and then invoke CallCommand either, as you will then will be unable to define the start and end point of the path.

You will have to write such functionality yourself.

Thank you for your understanding,
Ferdinand

Hello @DGLopez,

without any further questions or other postings, we will consider this topic as solved and flag it as such by Friday, 17/06/2022.

Thank you for your understanding,
Ferdinand