Roger Upole wrote:
Greg Ewing wrote:
Randy Syring wrote:
win32ui.error: The object has been destroyed.
I looked at this a while ago, and have a good idea where the
problem is. I'll try to get a fix in before the next build.
If it's because of the screwy things I'm doing to
get a dummy Py
Roger Upole wrote:
I looked at this a while ago, and have a good idea where the
problem is. I'll try to get a fix in before the next build.
BTW, posts about your project seem appropriate on the python-win32
mailing list to me, too.
Roger
FWIW, I have also appreciated the posts about
Greg Ewing wrote:
Randy Syring wrote:
I am still seeing the bug noted below in 2.1. Do you have plans to
tackle it?
>
win32ui.error: The object has been destroyed.
Reportedly it can be worked around by reverting to build
212 of pywin32. I haven't had a chance to investigate
what's causing
Randy Syring wrote:
I am still seeing the bug noted below in 2.1. Do you have plans to
tackle it?
>
win32ui.error: The object has been destroyed.
Reportedly it can be worked around by reverting to build
212 of pywin32. I haven't had a chance to investigate
what's causing it yet, sorry.
--
Greg,
I am still seeing the bug noted below in 2.1. Do you have plans to
tackle it?
Thanks.
--
Randy Syring
Intelicom
502-644-4776
"Whether, then, you eat or drink or
whatever you do, do all to the glory
of God." 1 Cor 10:31
David Robinow wrote:
On
On Wed, Jun 3, 2009 at 10:24 PM, Greg Ewing 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.
>
> Ha
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 cur
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?
Thanks.
--
Randy Syring
RCS Computers & Web Solutions
502-644-4776
http://www.rcs-comp.com
"Whether, then, you eat or drink o
Randy Syring wrote:
Could you tell me briefly how this project differs from something like
wxPython?
It wraps platform-specific libraries directly, rather than
being a wrapper around another cross-platform library. This
means less bloat and less dependencies. Chances are you
already have the n
Greg,
I have done some testing and reverting to pywin build 212 allows the demo to
run without the previously seen exception.
--
--
Randy Syring
RCS Computers & Web Solutions
502-644-4776
http://www.rcs-comp.com
"Whether, then, you eat or drink or whatever you
Greg,
I have tested 12-scroll.py on both Vista Professional and Windows XP Pro SP3
both with Python 2.5.4 and pywin build 213. Said test fails with the "the
object has been destroyed" exception.
--
--
Randy Syring
RCS Computers & Web Solutions
502-644-4776
htt
Greg,
Could you tell me briefly how this project differs from something like
wxPython?
Thanks.
--
--
Randy Syring
RCS Computers & Web Solutions
502-644-4776
http://www.rcs-comp.com
"Whether, then, you eat or drink or whatever you do, do all to the glory of
Go
PyGUI 2.0.5 is available:
http://www.cosc.canterbury.ac.nz/greg.ewing/python_gui/
More bug fixes for various platforms.
Still no idea what's causing the "object has been destroyed"
error on Windows XP, though. Does this happen for everyone?
Is there anyone who *has* got 12-scroll.py working f
13 matches
Mail list logo
