Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
openmesh-python
openmesh-python
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • OpenMesh
  • openmesh-pythonopenmesh-python
  • Issues
  • #10

Closed
Open
Opened Feb 19, 2018 by Janis Born@bornMaintainer

use new OpenMesh all_*s ranges to construct data arrays

OpenMesh!153 (merged) introduces a distinction between ranges that skip over deleted elements (e.g. mesh.vertices()) and those that include them (e.g. mesh.all_vertices()). As soon as we depend on this new version, we need to make sure to use the all_*s ranges for all exposed property access methods that return data as arrays. Otherwise, the entries of index arrays returned by *_indices will be invalid.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: OpenMesh/openmesh-python#10