Commit | Date | |
---|---|---|
[r27467]
by
bugman
Improved memory management in the relaxation curve-fitting GUI analysis. The peak intensity loading wizard is now properly destroyed. This is both via the delete() function |
2015-02-03 14:09:16 | Tree |
[r27466]
by
bugman
Improved GUI clean up when terminating GUI tests. The clean_up_windows() method, called from tearDown(), now also destroys the pipe editor window, the |
2015-02-03 14:02:41 | Tree |
[r27465]
by
bugman
Improved memory management in the NOE GUI analysis peak_wizard_launch() method. This method was just overwriting the self.peak_wizard object with a new object. However this does |
2015-02-03 13:58:20 | Tree |
[r27464]
by
bugman
Proper destruction of the peak analysis wizard of the NOE GUI analysis. The peak wizard's Destroy() method is now called and the self.peak_wizard object deleted in the NOE |
2015-02-03 13:56:21 | Tree |
[r27463]
by
bugman
Simplification of the GUI analysis post_reset() method. This now uses the delete_all() and hence delete_analysis() methods to clean up the GUI. The reset |
2015-02-03 13:51:32 | Tree |
[r27462]
by
bugman
Shifted the printouts from the GUI tests suite clean_up_windows() method to the tearDown() method. This change means that the printouts are not within a wx.CallAfter() call, but rather at the end of |
2015-02-03 13:11:32 | Tree |
[r27461]
by
bugman
Spacing printout for the list of still open GUI window elements. This is for the GUI test tearDown() method. |
2015-02-03 11:37:10 | Tree |
[r27460]
by
bugman
More fixes for the user function GUI object Destroy() method. This page GUI object is destroyed by the wizard window Destroy() method, so destroying again causes |
2015-02-03 11:31:23 | Tree |
[r27459]
by
bugman
Fixes for the user function GUI object Destroy() method. This matches the code just deleted in the GUI test suite tearDown() method for handing the user |
2015-02-03 11:29:02 | Tree |
[r27458]
by
bugman
The GUI test suite tearDown() method now calls the user function GUI wizard Destroy() method. This is for better handling of user function elimination. |
2015-02-03 11:28:05 | Tree |