From: Kevan H. <ha...@br...> - 2014-09-25 15:10:09
|
Dear Kevin, > Are these issues specific to Tcl/Tk on the Mac, or to Tcl itself? They are core issues with Tcl itself, on all platforms, and they are intentional. But the main event loop does perform graphics updates more agressively than "vwait" and "after", and Michiel informs me that there is a separate graphics event loop in tkMacOSXNotifer.c and tclMacOSXNotifier.c, which you say was designed by Daniel Steffen. So I doubt very much that this graphics event loop is plagued by the same limitation as the Tcl core event loop. Nevertheless, when a 2 GHz dual-core machine cannot draw windows fast enough, my guess is that something dysfunctional is going on in the communication with the OS. That's quite apart from the problem of the drawing being correct once it is complete. You say that the private APIs had fixed these problems, which suggests that the problems were not with the fundamentals of tkMacOSXNotifer.c and tclMacOSXNotifier.c. Are there places in the new API-free implementation where one large action has been broken into a large number of smaller actions? Yours, Kevan -- Kevan Hashemi, Electrical Engineer Physics Department, Brandeis University http://alignment.hep.brandeis.edu/ |