relax SVN archive

Temporary disabling of the memory management check in the GUI tests tearDown() method.

For some reason, it appears as if it is not possible to destroy wx Windows on MS Windows.

Fix for the GUI tests clean_up_windows() tearDown method.

After destroying all of the main GUI windows, a wx.Yield() call is made to flush the wxPython event
queue. This seems to help with the memory management.

Removed the wx.CallAfter() call in the GUI tests tearDown() method.

This was used to call the clean_up_windows() method. However the value of wx.Thread_IsMain() shows
that the tearDown() method executes in the main GUI thread. Therefore the wx.CallAfter() call for
avoiding racing conditions is not needed.

Changed the title for the user function GUI windows.

To better help identify what the window is, the title is now the user function name together with
text saying that it is a user function.

Popup menus are now properly destroyed in the GUI tests.

In many instances, the wx.Menu.Destroy() method was only being called when the GUI is shown. This
causes memory leaking in the GUI tests.

Added memory management checking to the GUI test suite tearDown() method.

If any top level windows are present, excluding the main GUI window and the relax controller, then a
RelaxError will be raised. Such a check will significantly help in future GUI coding, as now there
will be feedback if not all windows are properly destroyed.

The relax prompt window is now being destroyed by the GUI test suite tearDown() method.

The window is first closed in the tearDown() method and then destroyed in the clean_up_windows()
method.

Improved memory management for the GUI user function windows.

The Destroy() method will now destroy any Sequence or Sequence_2D windows used for the user function
arguments.

Improved memory management for the Sequence and Sequence_2D input GUI elements.

These are mainly used in the user function GUI windows. The dialogs are now destroyed before a
second is opened.

Better memory management for the missing data dialog in the GUI analyses.

The dialog is now stored as the class variable missing_data, and then is destroyed in the analysis
delete() method. Without this, the wxPython dialog would remain in memory for the lifetime of the
program.