9fc40b33de
* Fix source string mistakes reported on Crowdin * Update src/Mod/Draft/Resources/ui/TaskPanel_CircularArray.ui Co-authored-by: Roy-043 <70520633+Roy-043@users.noreply.github.com> * Update src/Mod/Draft/Resources/ui/TaskPanel_CircularArray.ui Co-authored-by: Roy-043 <70520633+Roy-043@users.noreply.github.com> * Update src/Mod/Draft/draftfunctions/upgrade.py Co-authored-by: Roy-043 <70520633+Roy-043@users.noreply.github.com> * Update src/Mod/Draft/draftfunctions/upgrade.py Co-authored-by: Roy-043 <70520633+Roy-043@users.noreply.github.com> * Update src/Mod/Draft/draftguitools/gui_downgrade.py Co-authored-by: Roy-043 <70520633+Roy-043@users.noreply.github.com> * Update src/Mod/Draft/Resources/ui/TaskPanel_SetStyle.ui Co-authored-by: Roy-043 <70520633+Roy-043@users.noreply.github.com> --------- Co-authored-by: Roy-043 <70520633+Roy-043@users.noreply.github.com>
2020 May
These modules provide supporting functions for dealing with the custom "scripted objects" defined within the workbench.
The functions are meant to be used in the creation step of the objects,
by the "make functions" in draftmake/, but also by the graphical
"Gui Commands" modules in draftguitools/ and drafttaskpanels/.
These functions should deal with the internal shapes of the objects,
or other special properties. They should not be very generic;
if they are very generic then they are more appropriate to be included
in the modules in draftutils/.
For more information see the thread: [Discussion] Splitting Draft tools into their own modules