On Mon, Jun 27, 2011 at 12:12, Paul McNett <[email protected]> wrote: > dabo Commit > Revision 6634 > Date: 2011-06-27 09:12:25 -0700 (Mon, 27 Jun 2011) > Author: Paul > Trac: http://trac.dabodev.com/changeset/6634 > > Changed: > U trunk/dabo/ui/__init__.py > U trunk/dabo/ui/uiwx/__init__.py > > Log: > I'm tired of receiving automated error reports with tracebacks that only > trace back to the wx.Notify() call from the dabo.ui.callAfter() and > dabo.ui.callAfterInterval() functions. I want to also see the trace > that lead to the callAfter*() call. > > So, this commit saves the current call stack in every callAfter() or > callAfterInterval() call. > > If it becomes a performance bottleneck, we could configure whether > to do this in dabo.settings, defaulting to False.
+1 from me. I have run into this before and it is frustrating not to have the full stack trace. Regards, Nate _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
