Menu

SVN archive Commit Log


Commit Date  
[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
results viewer window, and the prompt window. This ensures that all of the major relax windows are
destroyed between GUI tests.

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
not destroy the wxPython window. Now if a peak wizard is detected, its Destroy() method is called
before overwriting the object.

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
GUI analysis delete() method.

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
argument has been added to skip the manipulation of relax data store data, as the data store is
empty after a reset. However the calling of the delete_analysis() method now ensures that the
analysis specific delete() method is now called so that the GUI elements can be properly destroyed.

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
the tearDown() method just prior to starting the next test.

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
wxPython runtime errors.

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
function page object.

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
[r27457] by bugman

Fixes for the custom Wiz_window.Destroy() method.

This will now first close the wizard window via the Close() method to make sure all of the wizard
pages are properly updated. In the end the wizard DestroyChildren() method is called to clean up
all child wx objects, and finally Destroy() is called to eliminate the wizard GUI object.

2015-02-03 11:25:11 Tree
Older >
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.