Menu

SVN archive Commit Log


Commit Date  
[r27515] by bugman

Fix for the GUI wizard _go_next() method.

The way to determine if there are no more pages needs to be changed, as there are now no empty list
elements at the end of the wizard storage objects.

2015-02-04 15:28:04 Tree
[r27514] by bugman

Removed a debugging printout.

2015-02-04 15:22:22 Tree
[r27513] by bugman

Fix for GUI wizards and GUI user functions.

The recent memory management changes caused the wizard windows to have an incorrect layout so that
the wizard pages were not visible. Reperforming a layout of the GUI elements did not help. The
solution is to not initialise sets of max_pages of wx.BoxSizer elements in the wizard __init__()
method, but to generate and append these dynamically via the add_page() method. The change now
means that there are no longer multiple unused wx.BoxSizer instances generated for each wizard
window created.

2015-02-04 15:19:54 Tree
[r27512] by bugman

The maximum number of pages in the GUI wizard is no longer hardcoded.

The max_pages argument has been added to allow this value to be changed.

2015-02-04 14:49:30 Tree
[r27511] by bugman

Large memory management improvement for the relax GUI wizards and GUI user functions.

The pympler.muppy based memory management scripts in devel_scripts/memory_management for testing the
GUI user function windows was showing that for each GUI user function call, 28 wx._core.BoxSizer
elements were remaining in memory. This was traced back to the gui.wizards.wiz_objects.Wiz_window
class, specifically the self._page_sizers and self._button_sizers lists storing wx.BoxSizer
instances.

The problem was that 16 page sizers and 16 button sizers were initialised each time for later use,
however the add_page() method only added a small subset of these to the self._main_sizer wx.BoxSizer
object. But the Destroy() method was only capable of destroying the wx.BoxSizer instances
associated with another wxPython object. The fix was to add all page and button sizers to the
self._main_sizer object upon initialisation.

This will solve many memory issues in the GUI, especially in the GUI tests on Mac OS X systems
causing 'memory error' or 'bus error' messages and on MS Windows due to 'USER Object' and 'GDI
object' limitations.

2015-02-04 14:32:44 Tree
[r27510] by bugman

Created a script for testing the memory management when calling the time GUI user function.

2015-02-04 13:18:26 Tree
[r27509] by bugman

Removal of unused imports from the GUI user function memory testing scripts.

2015-02-04 13:15:25 Tree
[r27508] by bugman

Created a base class for the memory management scripts for the GUI user functions.

The core of the GUI_uf_minimise_execute.py script has been converted into the GUI_base.py base class
module. This will allow for new GUI user function testing scripts to be created.

2015-02-04 13:12:22 Tree
[r27507] by bugman

Shifted the memory_leak_test_GUI_uf.py script to devel_scripts/memory_management/GUI_uf_minimise_execute.py.

2015-02-04 12:58:17 Tree
[r27506] by bugman

Created the new devel_scripts/memory_management/ directory.

This will be used for holding all of the memory C module leak detection, GUI object leak detection,
memory management, etc. development scripts.

2015-02-04 12:57:37 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.