openMesh | OpenMesh source code learning and resources

Do existing OpenMesh iterators change, when I add elements?

Example code:

In OpenMesh, once a named property is added to an element, it will be permanent in the sense that the property survives the scope of the property manager as explained here. My question is, how to remove such a property by its name?

So far I tried removing by the property manager and even this one fails:

I have a function which finds the common neighbors of two vertices v1 and v2, i.e. those vertices that are connected to both v1 and v2:

I'm using OpenVolumeMesh and have so far been unable to figure out how to get the actual x, y, z coordinates from a VertexHandle. I have the following:

OpenMesh has the calc_dihedral_angle() function to calculate the dihedral angle between two faces. Is there a signed/directed equivalent of this function? Halfedges of faces are directed, thus normals of faces are well defined. It is thus meaningful to talk about the convexity.

Consider the following simple case, of only two connected faces. Starting from a zero dihedral (in-plane neighboring faces) one can rotate one of the faces around the common edge in either direction. In one case, the surface will be convex, in the other case, it will be concave. calc_dihedral_angle() does not differentiate between the two. I am looking for a function which takes this directionality into account and gives either a positive or a negative dihedral, depending on the convexity.

OpenMesh has its VectorT class which I believe is used to carry out all sorts of position vector operations (additions/subtractions, inner and outer products, etc.). Are there any examples available on how to actually use it? I would be in particular interested in

1. How to define and initialize a 3D vector of coordinates
2. How to properly convert a vertex position (of Point type) to a VectorT type, or, alternatively, how to get a vertex position as a VectorT type right away. So far I'm using mesh.point(vhandle) which, however, returns a Point() type.

Edit: Apparently Point is some kind of VectorT itself because the VectorT member functions work on Point objects as well.

I am building index and vertex buffers from OpenMesh structures which I will feed into my rendering engine. Here I iterate my elements (not shown) and create VertexHandles for each of my points and then add the face.

OpenMesh has its skipping iterators which skips elements marked for deletion. Is there an equivalent in circulators? I'm thinking circulators which treat mesh elements marked deleted as if they were not there any more. Note that this is not as simple as using the existing circulators and testing whether an element was marked for deletion because this does not take into account the changes in topology (neighboring elements, connected elements, etc) that would result from the deletion.

Is there a readily available function in OpenMesh that returns the edge handle connecting two vertices? For half edges there is the find_halfedge(vertex1, vertex2) function, but I could not find a corresponding find_edge(vertex1, vertex2) function. Currently I'm using my own, but I was wondering if there is any better way than this. Essentially I'm iterating over the surrounding edges of the two vertices and check where their halfedges point to: