-
-
Notifications
You must be signed in to change notification settings - Fork 401
Description
Hi,
I am really new to pythonocc and at the moment I am trying to prepare a - to some extent - automated mesh generation using the Gmsh-Python-API. For the visualization of my geometry, I am currently using pythonocc to read a "step" or "brep" file that I created with gmsh and visualize it using init_display from SimpleGui. Now, something strange happens: whenever I initialize the display with the init_display method, the behavior of Gmsh changes. After the initialization, I am not able to create the mesh anymore (some kind of binary error) and - what I think is really weird - to write a mesh that I generated before to a binary file. Somehow, Gmsh mixes up "," and "." in its file writing process, so that the written file is useless.
Are you aware of any changes to the environemt due to the initialization of the display with pythonocc? Maybe because both, Gmsh and pythonocc use the system occ libraries?