In this link, https://github.com/caceres/FreeCAD/commits/mat, there is a draft about the migration to model/view.yorik wrote: Basically you need to use a QTreeView instead of a QTreeWidget, and make a model yourself, which is the "entity" whick keeps/organizes the data of a tree widget, and give it a custom QStyledItemDelegate which handles the actions when you want to edit an item of the tree
Perhaps the end user must be allowed to define all characteristics of the custom properties[Name, Type, Value, Units, Constraints, Comments ...]
Hello. No. I don't achieve Gui::InputField working in the delegate class. For a strange reason after finish successful setEditorData, setModelData seems to lose the editor signal. I don't understand it.bernd wrote: ↑Sun Jun 10, 2018 4:07 am@damian:
do you still do some dev for material editor? What I would like to see is a nice Gui::Input field to change the material attributes, like we have in FEM
Do you do development in this regard? With such an input field in material editor, I would totally switch to the material editor for material editing in FEM.
Mhh strange we do not have this problem in FEM material task panel ...
What do you mean by this?