You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The workflow in FreeCAD is suboptimal for parametric design. While designing, the user may want to create a parameter, for example for a Pad on a Sketch. As soon as the user decides how to name the parameter, the user has to temporarily abort the Pad task and go to some document object or a spreadsheet to create the parameter.
In case of a document object, the user has to choose a document object, create a property which of itself has a limited workflow as discussed in #13038. In case of a spreadsheet, the user has to go to the spreadsheet of choice, create a cell with a name for the parameter, create another cell (preferably close by, for example the next column) with the value, then add an alias to the cell that matches the name of the first cell (making sure the names are the same).
Then for both of these situations, the user has to remember how to access these variables (the path to the variables), going into the Pad task again, click on the expression symbol and type the path of the expression (for example file#Spreadsheet.Height).
The main issue is that users cannot add a parameter while still in the design task, therefore discouraging parametric design.
An obvious solution to this workflow problem is to create the parameters before doing the design. However, unless it is very clear beforehand what the constraints of the design are, it is common to encounter situations that would benefit from having parameters. These situations are subsequently hampered by the limitations of workflow just described.
Adding new data elements from Sketcher and other WBs should be simple and obvious.
Related
The Sketcher workbench has limited support to add properties while designing: It allows the user to name a constraint. However, this is not a general approach that works beyond the Sketcher workbench, the entered name is not a direct property of the Sketch, but a property inside the property Constraints within the Sketch. Moreover, the user cannot choose where to store the parameter, it has to reside in the Constraints property within the Sketch.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
FYI I've started a currently named Expression Manager macro to list all the expressions of a document, another tab will show named constraints.
It could has a third tab to list custom properties but it seems there is currently no way to know if a property is user created. EDIT: getPropertyStatus returns 21 for dynamically added properties
Thanks for letting me know. I think this comment is more fitting to issue #13038. Looks great and it seems we think alike. I've just created PR #13112. Please let me know what you think.
Is there an existing issue for this?
Problem description
The workflow in FreeCAD is suboptimal for parametric design. While designing, the user may want to create a parameter, for example for a Pad on a Sketch. As soon as the user decides how to name the parameter, the user has to temporarily abort the Pad task and go to some document object or a spreadsheet to create the parameter.
In case of a document object, the user has to choose a document object, create a property which of itself has a limited workflow as discussed in #13038. In case of a spreadsheet, the user has to go to the spreadsheet of choice, create a cell with a name for the parameter, create another cell (preferably close by, for example the next column) with the value, then add an alias to the cell that matches the name of the first cell (making sure the names are the same).
Then for both of these situations, the user has to remember how to access these variables (the path to the variables), going into the Pad task again, click on the expression symbol and type the path of the expression (for example
file#Spreadsheet.Height
).The main issue is that users cannot add a parameter while still in the design task, therefore discouraging parametric design.
An obvious solution to this workflow problem is to create the parameters before doing the design. However, unless it is very clear beforehand what the constraints of the design are, it is common to encounter situations that would benefit from having parameters. These situations are subsequently hampered by the limitations of workflow just described.
Full version info
Subproject(s) affected?
Core
Anything else?
Context
Related
The Sketcher workbench has limited support to add properties while designing: It allows the user to name a constraint. However, this is not a general approach that works beyond the Sketcher workbench, the entered name is not a direct property of the Sketch, but a property inside the property Constraints within the Sketch. Moreover, the user cannot choose where to store the parameter, it has to reside in the Constraints property within the Sketch.
Code of Conduct
The text was updated successfully, but these errors were encountered: