On Wed, Jun 3, 2009 at 10:24 PM, Greg Ewing<greg.ew...@canterbury.ac.nz> wrote: > Randy Syring wrote: >> >> I am wondering if the problems with build 213 have ever been resolved on >> Windows. Or was I mistaken that build 213 was the problem? > > I don't know. I haven't heard any more about it from > anyone since then. > > Has anyone else out there that's having this problem > successfully cured it by reverting to 212? > > If so, I could look into what's changed between 212 > and 213 to see if it gives any clue to what's going > on. > I have. The problem exists using Python 2.5.4 and Python 2.6.2 on Windows XP Professional and Windows Vista Home Premium. No problems with 212. See below for what happens using 213. Reverting to 212 works fine.
c:\home\PyGUI-2.0.5\Tests>\python26\python 12-scroll.py Traceback (most recent call last): File "12-scroll.py", line 38, in <module> win = TestWindow() File "12-scroll.py", line 9, in __init__ width = 300, height = 300, scrolling = 'hv') File "c:\home\PyGUI-2.0.5\Tests\TestScrollableViews.py", line 16, in __init__ ScrollableView.__init__(self, **kwds) File "c:\home\PyGUI-2.0.5\GUI\Win32\ScrollableViews.py", ilne 31, in __init__ GScrollableView.__init__(self, _win = win) win32ui.error: The object has been destroyed. c:\home\PyGUI-2.0.5\Tests> _______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32