openmesh-python merge requestshttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests2022-10-13T14:41:05Zhttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests/9Fixed typos2022-10-13T14:41:05ZJan Möbiusmoebius@cs.rwth-aachen.deFixed typosJan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests/8Track om master2022-10-13T14:37:12ZJan Möbiusmoebius@cs.rwth-aachen.deTrack om masterJan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests/6Pybind update2022-03-07T14:16:01ZJan Möbiusmoebius@cs.rwth-aachen.dePybind updateJan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests/4Implement reading/writing entity status and expose feature bit2022-03-07T13:37:16ZMartin HeistermannImplement reading/writing entity status and expose feature bitHi,
I just needed to mark and save features in a mesh and hacked in the essentials for that.
I hope this is useful as-is, but I'd be happy to make changes/improvements.Hi,
I just needed to mark and save features in a mesh and hacked in the essentials for that.
I hope this is useful as-is, but I'd be happy to make changes/improvements.https://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests/3Update pybind11 to 2.6.12022-03-07T13:22:33ZJan Möbiusmoebius@cs.rwth-aachen.deUpdate pybind11 to 2.6.1Jan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests/7Obj textures2022-03-07T13:19:42ZJan Möbiusmoebius@cs.rwth-aachen.deObj texturesJan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests/5Updates2022-03-07T11:48:49ZJan Möbiusmoebius@cs.rwth-aachen.deUpdatesJan Möbiusmoebius@cs.rwth-aachen.deJan Möbiusmoebius@cs.rwth-aachen.dehttps://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests/1Remove property maps2019-03-06T03:32:12ZMatthias MöllerRemove property mapsHi,
the MeshWrapper class defines some property maps, which maps the names of all the python-defined properties to the corresponding property handles.
I guess they are redundant, since you can do everything with the core OpenMesh functi...Hi,
the MeshWrapper class defines some property maps, which maps the names of all the python-defined properties to the corresponding property handles.
I guess they are redundant, since you can do everything with the core OpenMesh functions.
This MR has an implementation using only OpenMesh functions.https://gitlab.vci.rwth-aachen.de:9000/OpenMesh/openmesh-python/-/merge_requests/2fix pythonpath by using generator expression2018-05-08T15:51:14ZMatthias Möllerfix pythonpath by using generator expressionWith multi-configuration/crossplatform toolchains, the output path of a target varies from the selected configuration (most famous: Debug/Release on MSVC/xcode).
Therefore, the module's output path is not the bin dir, but mostly in somet...With multi-configuration/crossplatform toolchains, the output path of a target varies from the selected configuration (most famous: Debug/Release on MSVC/xcode).
Therefore, the module's output path is not the bin dir, but mostly in something like `${CMAKE_CURRENT_BINARY_DIR}/Debug` or `${CMAKE_CURRENT_BINARY_DIR}/Release`.
This MR fixes the path, so that pythonpath is always set to the correct path where the module was built into.