Re: sorry, pyLbc again
- From: "qubit" <lauraeaves@xxxxxxxxx>
- To: <programmingblind@xxxxxxxxxxxxx>
- Date: Sun, 11 Jul 2010 18:11:43 -0500
This means you have an infinite recursion in your code. Perhaps that is not
the event your handler was defined to handle.
Your runtime stack is overflowing because you don't have a condition in some
function that will halt the recursion. Check all the functions that are
recursive and see if you may have omitted something.
This is a common type of bug. Everyone codes an infinite recursion sometime
when learning to program.
--le.
----- Original Message -----
From: "Alex Hall" <mehgcap@xxxxxxxxx>
To: "programmingblind" <programmingblind@xxxxxxxxxxxxx>
Sent: Sunday, July 11, 2010 5:47 PM
Subject: sorry, pyLbc again
Hi all,
Sorry for all the pyLbc posts, but this one is quite confusing. I have
a custom event handler defined for a dialog. However, the error keeps
coming up as lbc.py, line 478, in DefaultHandler. I am not sure why
that would be called if I have my own event handler?
Anyway, the error is also confusing: maximum recursion depth exceeded.
The line is
window = self.FindWindowByName(control)
I had not seen this error before today (until now, everything was
working fine), and I cannot see what I changed. I tried to up things
back just as they were yesterday, when everything was working, but I
still have no luck. Thoughts? TIA.
--
Have a great day,
Alex (msg sent from GMail website)
mehgcap@xxxxxxxxx; http://www.facebook.com/mehgcap
__________
View the list's information and change your settings at
http://www.freelists.org/list/programmingblind
__________
View the list's information and change your settings at
http://www.freelists.org/list/programmingblind
Other related posts: