GitLab

(cherry picked from commit 80964422)

Split 'std::vector< std::pair< int, int > > keys' into 'std::vector< int > typeKeys' and 'std::vector< std::size_t > entityKeys'

use two optional vectors to specify the elements and the partitions in mesh::partition() instead of a vector of pairs: it's more in line with what we do elsewhere in the api

if a mesh already exists, make ReorientMesh and setOutwardOrientation() change its orientation in addition to setting the reverse orientation flag (cf. #1306)

new optional parameter in model::isInside to choose if the check is performed using parametric coordinates (the default) or model coordinates

- new fltk/openTreeItem and fltk/closeTreeItem api functions to manipulate the menu through the api

in addition to the default camelCase function names, add snake case aliases in the Python and Julia API, as this is the recommended style in these languages

get{Edge,Face}Number -> get{Edge,Face}Tags for consistency + remove experimental warning, as this is here to stay

make edge identifiers size_t + fix arguments of mesh/getEdgeNumber + add mesh/getFaceNumber (these should be renamed...)

new (probably temporary) gmsh/mesh/createEdges and gmsh/mesh/createFaces (until we provide a facility to simply create and store mesh edges/faces as elements)

interface old "geometrical" boundary layers from the built-in kernel in the api; these can still be useful for modelling (compared to classical "mesh-based" boundary layers, which do not create model entities and are simply meshing constraints)

- make sure not to break backward compatibility (coef should be > 0; .geo files encode direction in type)
- add "Beta" law in api