You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can I assume that in the list of halfedges returned by halfedge_handles(), each even-indexed halfedge is followed by its opposite halfedge? I saw in the assignement operator implementation that it seems to be the case, but is it documented somewhere?
When copying a HDS (using the assignement operator mentioned above, or the copy constructor), is the order of the halfedges preserved? If yes (the code seems to say it is), is it guaranteed in all cases? It could be nice to document it. In my case, I have a list of object that is stored separately. Each object stores a halfedge handle pointing to the halfedge it is attached to. I need to backup the HDS and this list, and I want a efficient way to restore the link between the objects and the HDS.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I have two questions regarding the HDS:
halfedge_handles()
, each even-indexed halfedge is followed by its opposite halfedge? I saw in the assignement operator implementation that it seems to be the case, but is it documented somewhere?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions