Hi Troels,
Could you give a complete set of step-by-step instructions for how to
replicate this? I would like to convert these steps into a GUI test
so that I can replicate the problem. This is a common problem with
wxPython - a GUI change that works perfectly on one operating system
fails on another. With a GUI test, I'll then be easily able to check
this behaviour on Linux, Mac and Windows.
Cheers,
Edward
On 29 May 2014 15:29, Troels Emtekær Linnet <tlinnet@xxxxxxxxxxxxx> wrote:
Hi Ed.
After your changes, I still get:
Traceback (most recent call last):
File
"/Users/tlinnet/software/relax_trunk/gui/input_elements/sequence_2D.py",
line 113, in open_dialog
self.selection_win_show()
File
"/Users/tlinnet/software/relax_trunk/gui/input_elements/sequence_2D.py",
line 134, in selection_win_show
self.sel_win.Close()
File
"/Library/Frameworks/Python.framework/Versions/7.3/lib/python2.7/site-packages/wx/_core.py",
line 14564, in __getattr__
raise PyDeadObjectError(self.attrStr % self._name)
wx._core.PyDeadObjectError: The C++ part of the Sequence_window_2D object
has been deleted, attribute access no longer allowed.
When I try to use the dx.map functionality.
_______________________________________________
relax (http://www.nmr-relax.com)
This is the relax-devel mailing list
relax-devel@xxxxxxx
To unsubscribe from this list, get a password
reminder, or change your subscription options,
visit the list information page at
https://mail.gna.org/listinfo/relax-devel
Re: Problems with GUI and dx.map