Hallo new user, Furthermore, imagine that a large amount of data is being received over a slow connection. Socket 1 has no data in the read buffer, so it calls wxYield. There is still a pending event on Socket 2, so wxWidgets attempts to process that event. However, that event cannot complete, and it also calls wxYield. This will cause the infamous “wxYield called recursively” message to appear. Eventually the stack would fill up with recursive calls to wxYield as long as all the data has not yet arrived and the call stack cannot unwind. Many users immediately assume that this error message indicates a flaw in wxWidgets, when the truth is that it represents a problem in the application code. Simply stated, applications should be programmed so that this situation does not occur; the error is present to reveal a problem in the application code so that it can be fixed.
Please complete one event completely before calling the other event -- View this message in context: http://www.nabble.com/new_user-matplotlib-help-tp15373200p19665311.html Sent from the matplotlib - users mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
