OpenMesh issueshttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/OpenMesh/-/issues2018-12-06T08:20:56Zhttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/OpenMesh/-/issues/56Mention new OM python bindings in Documentation2018-12-06T08:20:56ZMartin HeistermannMention new OM python bindings in Documentationhttps://www.openmesh.org/Daily-Builds/Doc/a00036.html only describes the old python bindings, which can lead to confusion (see OM mailing list on 2016-06-08), I think we should (very visibly) refer to the new bindings there.https://www.openmesh.org/Daily-Builds/Doc/a00036.html only describes the old python bindings, which can lead to confusion (see OM mailing list on 2016-06-08), I think we should (very visibly) refer to the new bindings there.Isaak LimIsaak Limhttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/OpenMesh/-/issues/27document that DecimaterT::decimate does not trigger a garbage collection2017-05-01T10:16:22ZJanis Borndocument that DecimaterT::decimate does not trigger a garbage collection`DecimaterT::decimate` removes mesh entities but does not trigger a garbage collection. It is expected that a user manually calls `garbage_collection` afterwards.
As indicated by [this question on StackOverflow](http://stackoverflow.com...`DecimaterT::decimate` removes mesh entities but does not trigger a garbage collection. It is expected that a user manually calls `garbage_collection` afterwards.
As indicated by [this question on StackOverflow](http://stackoverflow.com/questions/38483848/openmesh-decimater-does-not-reduce-vertex-number), this is unexpected and causes some confusion.
The fact that `DecimaterT::decimate` does not prompt a garbage collection should be properly documented.https://gitlab.vci.rwth-aachen.de:9000/OpenMesh/OpenMesh/-/issues/15Create a more usefull example for the mesh decimater2017-06-30T14:05:35ZJan Möbiusmoebius@cs.rwth-aachen.deCreate a more usefull example for the mesh decimaterThe current doc only contains how to setup the decimation order without any constraint on the quality. We should extend the example with a module controlling the decimation quality.The current doc only contains how to setup the decimation order without any constraint on the quality. We should extend the example with a module controlling the decimation quality.Daniel GotzenDaniel Gotzenhttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/OpenMesh/-/issues/14Document deletion process2017-05-01T10:16:22ZJan Möbiusmoebius@cs.rwth-aachen.deDocument deletion process
Add documentation about deletion:
Halfedges are updated on the fly, entities removed later.
Circulators ignore deleted entities, iterators only if skipping, ...
See Mailing list for some more info
Add documentation about deletion:
Halfedges are updated on the fly, entities removed later.
Circulators ignore deleted entities, iterators only if skipping, ...
See Mailing list for some more info
https://gitlab.vci.rwth-aachen.de:9000/OpenMesh/OpenMesh/-/issues/11Documentation2017-10-27T14:34:54ZJan Möbiusmoebius@cs.rwth-aachen.deDocumentationSeems to be currently broken in Daily buildsSeems to be currently broken in Daily buildsOpenMesh 6.0https://gitlab.vci.rwth-aachen.de:9000/OpenMesh/OpenMesh/-/issues/10Mark the circulators without direction indicator as deprecated e.g. with the ...2017-06-30T14:05:35ZJan Möbiusmoebius@cs.rwth-aachen.deMark the circulators without direction indicator as deprecated e.g. with the given info belowThe circulator without orientation is deprecated and you should use the new implementation with the given directions. This change was in the OpenMesh 4.0 changelog.
To not break existing code, we still have the old one in place. But ...The circulator without orientation is deprecated and you should use the new implementation with the given directions. This change was in the OpenMesh 4.0 changelog.
To not break existing code, we still have the old one in place. But it has some problems such as visiting entities twice when using the decrement operator.
If you use the ones with the direction specified, you are safe and get slightly better performance.