Open ddamadori opened 1 year ago
Not sure why it does not show up in the TUI interface, will need to take a look. For sure none of the meshing TUI is under consideration for the settings API yet. Not sure if we will migrate it there or not since most customers would be using the workflows, presumably.
Hi Dan,
Thanks for the feedback.
May I ask why this migration is not considered?
In my humble opinion there is no doubt that Settings API is clearly the way to go for on the long term, and that is also the message we deliver to the customers, at least for the solver part.
Thank you,
Dario
Yes, you are totally right and it is under consideration. Note in my post it says 'yet'. Migrating the meshing TUI -> Settings API requires an investment into Fluent meshing that's not gotten on the priorities yet for the Fluent meshing team relative to all the other things they are asked to do. It's not that it wont happen, it's just about when.
A workaround is to pass the TUI commands as arguments of the parent command: meshing.tui.display.views("list-views")
@mkundu1 I have explicitly placed this on the backlog
š Before submitting the issue
š Description of the bug
the class ansys.fluent.core.session_meshing.Meshing.tui.display does not have all the commands that should be under views, meaning that ansys.fluent.core.session_meshing.Meshing.tui.display.views is missing.
The equivalent in the TUI is the following:
It is also completely missing from the Settings API for the moment.
š Steps to reproduce
create a meshing session and try to access session.display.view
š» Which operating system are you using?
Windows
š Which ANSYS version are you using?
231
š Which Python version are you using?
3.7
š¦ Installed packages