They are sorted but I got different order for some vertex where the list of connected vertex is shifted (+1) compared to connected edges. Simply I´m not sure if that works as expected. Thanks.
In a Rhino Mesh object, vertices and topologyvertices are two different things.
For each topologyvertex there might be more than one vertex.
In case of a fully welded mesh, the two list are congruent.
In addition to what Riccardo states have in mind that Vertices are pts (float coords) on a per Face basis while TVertices are pts (also floats) on a per Mesh basis. Meaning that indexing differs … but there’s R Methods from/to. Meaning that for a Mesh with no Vertices.CombineIdentical() applied is possible one TVertex to point to more than one Vertex (same pos diff owner, so to speak). Have also in mind that Vertex Normals are using the Vertices indexing.
That said … I always use TVertices when doing Connectivity Trees (V, E, F). For instance:
BTW: If Normals are required the cost of “index mapping” is almost nothing.
Thank you for the answers, however the mismatching I´m pointing is not related to vertices and topological vertices but connected VERTICES and connected EDGES matching.
In my particular case I´m using MeshTopologyVertexList and MeshTopologyEdgeList classes. After that I did some logic to match them. As I said, I´m not sure if that´s working as expected.
For reference I found this post
Explain in depth what you want to do AND post your code (if in C# I can fix it in no time - if in P wait for some other user).