On Aug 10, 2007, at 12:58 AM, johnf wrote:
> Any suggestions on were to start. I assume that this issue is not
> in the form
> but from the Dabo framework - right?
I wouldn't assume either.
If you have any code in your forms that deal with closing behavior,
add some print statements there. Also uiApp.onFileExit() is another
good place.
In dFormMixin, you should add prints to __onClose(), __onWxClose(),
release() and close(). In dForm, add them to _beforeClose() and
confirmChanges(). With any luck, that should at least reveal a clue
as to what part of the process is triggering the segfault.
Also, since the forms will be in various states of destruction, you
can't reliably write code like: print self.Name, since 'self' may
refer to a dead object. Instead, write your statements like:
if self:
print self.Name,
else:
print "DEAD",
print "entering dFormMixin.__onClose"
This way you don't add to the mix of errors.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
