This section discusses the creation and saving of the GUI module and the support module. I want to make saving simple and intuitive while reducing the probability of inadvertently overwriting hard to reproduce code, particularly in the support module. At the same time I did not want to bombard the user with “Are you sure ...” dialogues. These goals are somewhat contradictory. I would appreciate comments on this subject.
Here is what I have tried to implement:
When one chooses to generate the GUI module (Control-P):
When one chooses to generate the Support module (Control-I):
The constructed GUI is transformed into a Tcl file and saved if the GUI has changed in the current session.
If there is no existing support module, then one is generated, displayed in the Python Console, and automatically saved.
If there is an existing support module, action is a bit more elaborate. First, the existing support module is analyzed to see what Tk variable and functions are defined in the existing module and compared with those which would be defined in a new support module. Next, the user is given the choice
- use the existing support module, thereby preserving your hand written code,
- generate a new support module,
- update the existing support module updated to include the additional Tk variable and skeleton functions.
From the Python Console, the user can select the Save button and the GUI module will be saved if “new”.
From the Python Console, the user can select the Run button which provides the same function as the Save button but also attempts to execute the GUI module.