The new version of PrePoMax contains the following features:
Download: Downloads – PrePoMax
The Mesh Refinement mesh setup item was renamed to Local Mesh Size. It supports local mesh size definition based on the number of elements. This works correctly only for Gmsh and only if structured-quad algorithms are NOT used. There is no direct way to enforce a certain number of elements for the Netgen mesher.
Interesting subject, NetGen mesher for refinement.
You can refine by element size, right? So, similar to n_elements? You visualise the highlight in red on display?
Then, when I try in NetGen to use this smaller size setting and the global setting has a larger MIN size, the refinement doesn’t do anything, I think? Is there a way that the setting on refinement with a small size overwrites the Global MIN size, w/out having to go back/forth between the settings in tree?
No, currently the global mesh sizing is dominant. I will have to look into it to know why it was designed that way. I think Netgen works in this way internally.
The mesh preview of the Local Mesh Size shows the effect of the given value only. It does not reflect the global setting. If the global setting were taken into account, the user might feel that nothing changes after changing the local mesh size.
it seems display model symbols not working as previously in this development versions, changing to None, Model or Step have not affected.
You are right. I will have to fix this.