"Larry W. Virden" <lvirden@gmail.com> writes: >I do hope that anyone who is planning on upgrading to Tcl/Tk 8.5 (with >the new gui widget set, etc.) has checked out at least one of the >release candidate releases and reported problems encountered. I tried 8.5rc2 in our application that uses Tk via Python, and I'm seeing some weird behavior, like text widgets where the text isn't selectable and sometimes you can't type into it, but if I iconify and deiconify the dialog, then I can type in it again (but the text is still unselectable). I also noticed that for the Tk Aqua version, that 8.4.16 and 8.5 changed something with threads and our Python application regularly crashes with a treading error, so we've dropped the Aqua version. In both cases, I haven't had time yet to dig in and figure what's really wrong. But I will be monitoring the newsgroup and reading about other folks' experiences with 8.5. Greg Couch UCSF Computer Graphics Lab

Greg Couch wrote: > "Larry W. Virden" <lvirden@gmail.com> writes: > >>I do hope that anyone who is planning on upgrading to Tcl/Tk 8.5 (with >>the new gui widget set, etc.) has checked out at least one of the >>release candidate releases and reported problems encountered. > > I tried 8.5rc2 in our application that uses Tk via Python, and I'm seeing > some weird behavior, like text widgets where the text isn't selectable and > sometimes you can't type into it, but if I iconify and deiconify the dialog, > then I can type in it again (but the text is still unselectable). Can you show a simple test case? I wonder what is causing this. I know that <<Modified>> is being fixed in the Tk text widget today, and yesterday. There's also the bug I posted about with Tk_RedrawImage, which looks like it may not be fixed by the time of 8.5.0. > I also noticed that for the Tk Aqua version, that 8.4.16 and 8.5 changed > something with threads and our Python application regularly crashes with > a treading error, so we've dropped the Aqua version. Are you using Tk in more than 1 thread? It doesn't work well in general to use Tk in more than thread. A test case for this would also be useful. What is the threading error you see? > In both cases, I haven't had time yet to dig in and figure what's really > wrong. But I will be monitoring the newsgroup and reading about other > folks' experiences with 8.5. I once generated some statistics years ago, and found that a large portion of the Tcl and Tk sources have changed between the 8.4 and 8.5 release > 50% IIRC. It's probably even larger now. My statistics were meant to push the Tcl Core Team for more releases, but Jeff Hobbs at the time felt there weren't enough new features to warrant a release. I'm personally hoping that 8.5/8.6 is eventually a better release than 8.4, but most people don't run the HEAD, and with the core team being uhm difficult it's frustrating. Note: I'm not condemning all of the core team. DGP has certainly been pushing for releases, and replying to 4 year old bug reports assigned to TCT members that seemingly don't have the time. KBK has wanted 9.0 for years. In my opinion, the Tcl/Tk core test suites give *some* TCT developers a false sense of security. It's very difficult to fully test code paths, especially when so many changes have occured since 8.4. You may recall that I was searching for more Tcl developers to fix bugs years ago, and posting on comp.lang.tcl to motivate people. Nothing came of it, and I was highly disappointed. So some of you have no one to blame but yourselves. Shame on you :) George

Greg Couch wrote: > George Peter Staplin <georgepsSPAMMENOT@xmission.com> writes: > > If I had a simple test case for the unselectable text, I'd file a bug > report. If you're familiar with Python, it is with the IDLE window. > > As for Aqua, we only use Tk in one thread because Python enforces that > automatically. I don't have access to Mac OS X today, but the error was > something like: "Fatal Python error: PyEval_ReleaseThread: NULL thread state" > and then Python exited. That indicates something changed with threading > on Aqua since the identical code is used for Windows and X11 and it works > on those platforms (and for Aqua in Tk 8.4.15). > > - Greg I was kind of hoping to nudge you for more info, and I got it. I'll try to build a simple test case using Python and the latest Tk. I'm familiar with IDLE. It's the editor extraordinaire for Python that comes with Python and uses Tkinter. IIRC Guido van Rossum wrote most of it. I can't be of help with the MacOS X problems yet. George

George Peter Staplin wrote: > Greg Couch wrote: >> >> If I had a simple test case for the unselectable text, I'd file a bug >> report. If you're familiar with Python, it is with the IDLE window. >> >> As for Aqua, we only use Tk in one thread because Python enforces that >> automatically. I don't have access to Mac OS X today, but the error was >> something like: "Fatal Python error: PyEval_ReleaseThread: NULL thread state" >> and then Python exited. That indicates something changed with threading >> on Aqua since the identical code is used for Windows and X11 and it works >> on those platforms (and for Aqua in Tk 8.4.15). >> >> - Greg > > I was kind of hoping to nudge you for more info, and I got it. I'll try > to build a simple test case using Python and the latest Tk. > > I'm familiar with IDLE. It's the editor extraordinaire for Python that > comes with Python and uses Tkinter. IIRC Guido van Rossum wrote most of > it. > > I can't be of help with the MacOS X problems yet. I can duplicate the bug with 8.5/HEAD of Tcl and Tk using the latest Python from python.org with IDLE. I'm trying to track it down now. George