From: Russell O. <ro...@uw...> - 2014-12-08 21:28:48
|
On 12/5/14 6:40 PM, Kevin Walzer wrote: > On 12/5/14, 7:54 PM, Russell Owen wrote: >> Clearly this is merely a cosmetic annoyance. Nonetheless, I'm reporting >> it and asking if anyone can suggest a reasonable workaround. The only >> one I've thought of, so far, is to hide widgets using grid.forget >> instead of grid.remove (I have not verified that works, but I'd be >> amazed if it didn't). That's a bit of a nuisance because I'll have to >> record the grid parameters, but it's certainly doable. If anyone has a >> better idea I'd love to hear it. > > I'm aware of issues like this; they are likely a side effect of my > removing the private Cocoa API calls from Tk that are a big no-no under > Apple's guidelines but which undeniably improved the drawing > performance. In other words, removing them has resulted in degraded > drawing performance, which is why they were put there in the first place. > > It's a tough call, but as I discussed on the list a few months ago, I > think keeping them in there was simply a bad idea because Apple's > distribution channels so strongly discourage them. The Mac App Store > rejects any apps making use of private API calls, for instance. > > I don't know of a way to substantially improve drawing performance; I > (and other contributors) have spent a lot of time tweaking things and > fixing the worst of the bugs, but that won't change the fundamental > issue. I'm sorry about that. It's a lousy situation, and I wish Apple's > guidelines did not put us in this position. I appreciate all the work you have put into Aqua Tk and we can certainly live with the flicker. -- Russell |