| | |
| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | """Modules that define classes that handle task panels of the GuiCommands. |
| | |
| | These classes load `.ui` files that will be used in the task panels |
| | of the graphical commands defined in the `draftguitools` submodules. |
| | These classes also define the callbacks and interactions of the widgets |
| | in the `.ui` files. |
| | |
| | The task panel interface should be, in the possible, not manually written |
| | in Python. Rather a `.ui` file should be built using Qt Designer, |
| | and should be placed in the `Resources/ui/` directory so that it is loaded |
| | by the respective task panel class. |
| | |
| | :: |
| | |
| | class CommandTaskPanel: |
| | def __init__(self): |
| | ui_file = ":/ui/TaskPanel_OrthoArray.ui" |
| | self.form = Gui.PySideUic.loadUi(ui_file) |
| | |
| | At the moment, most GuiCommands don't have their own `.ui` file, |
| | nor task panel class. Instead their task panels are completely defined |
| | by the `DraftGui` module. |
| | |
| | This should be changed in the future because `DraftGui` |
| | is a very large module, and creates many different widgets |
| | and handles many callbacks, making it difficult to extend and maintain. |
| | This module selectively chooses the widgets to show and to hide |
| | depending on the command that is activated. |
| | |
| | Individual task panel classes and `.ui` files are more maintainable |
| | because changes can be done to a single tool without affecting the rest, |
| | and the module size is kept small. |
| | """ |
| | |
| | |
| | |
| |
|