Sometimes (always consistently in the same spot however), the following
snippet of code manages to set ‘raiser’ to a wxPyDeadObject:
raiser.GetEventHandler().
AddPendingEvent(evt)
In
other words, I’m stepping through this code when I arrive at this line,
“raiser” is a Dialog Box. I step into it which brings me into the wx
code. Hitting “step into” again brings me back to where I started,
although “raiser” is now a wxPyDeadObject.
I can’t imagine what is going on that would cause this to happen.
Nor can I see why it doesn’t happen in other cases. Any ideas?
Thanks,
Tim
Tim Mahrt
University of Illinois
Linguistics Dept. Graduate Student
Sorry. I guess I just needed to sleep on it. The issue was a race condition.
Thanks,
Tim
Tim Mahrt
University of Illinois
Linguistics Dept. Graduate Student
···
On Sun, Feb 1, 2009 at 1:46 AM, Tim Mahrt timmahrt@gmail.com wrote:
Sometimes (always consistently in the same spot however), the following
snippet of code manages to set ‘raiser’ to a wxPyDeadObject:
raiser.GetEventHandler().
AddPendingEvent(evt)
In
other words, I’m stepping through this code when I arrive at this line,
“raiser” is a Dialog Box. I step into it which brings me into the wx
code. Hitting “step into” again brings me back to where I started,
although “raiser” is now a wxPyDeadObject.
I can’t imagine what is going on that would cause this to happen.
Nor can I see why it doesn’t happen in other cases. Any ideas?
Thanks,
Tim
Tim Mahrt
University of Illinois
Linguistics Dept. Graduate Student