|
Mon, Jan 13 2003
09:50:27
|
|
Request created by frank
|
|
Subject: Dialog closing sequences
Authenticate Dialog: Due to a slow database connection I could
manage to click the OK button twice - which results in a wxPython error,
see below. This has also to be evaluated for other dialogs and potentially
the sequences have to be changed so first the dialog is closed and than
further database actions are performed.
[Debug] 09:43:27: C++ assertion "wxAssertFailure" failed in
../src/gtk/dialog.cpp(234): wxDialog:EndModal called twice
An unhandled exception occurred:
Traceback (most recent call last):
File "./Greater/Dialogs/authenticate.py", line 115, in OnOK
self.end_dialog(wxID_OK, ( self.d.GetValue(),
File "./Greater/Dialogs/authenticate.py", line 124, in end_dialog
self.EndModal(wx_result)
File "/spare/sandbox/wx-20021119/site-python2.1/wxPython/frames.py", line
172, in EndModal
val = apply(framesc.wxDialog_EndModal,(self,) + _args, _kwargs)
wxPyAssertionError: C++ assertion "wxAssertFailure" failed in
../src/gtk/dialog.cpp(234): wxDialog:EndModal called twice
|
|
|
Thu, Jan 16 2003
15:00:23
|
|
Status changed to resolved by jan
|
|
|
Thu, Jan 16 2003
15:00:23
|
|
Comments added by jan
|
|
the cleaning up of temporary sessions is now done after the dialog
is closed. This should make it almost impossible to reproduce the bug.
I therefore resolve it.
However, a real solution probably would be to diable/enable the dialog for the
authentication test. |
|