Re: [python-win32] FireEvent : comtypes work but win32com fails, why?

2008-06-24 Thread Mark Hammond
> > In summary, there are one big problem and one minor problem. The > > first > > is about pywin32's inability to pass FireEvent's second argument. I can't explain that :( I've stepped through the code, and it seems we are passing a VT_VARIANT containing a VT_BYREF|VT_DISPATCH. I'm afraid I'm n

Re: [python-win32] FireEvent : comtypes work but win32com fails, why?

2008-06-24 Thread June Kim
2008/6/25 June Kim <[EMAIL PROTECTED]>: > IE's FireEvent works with a single argument, for example, > FireEvent("onKeyUp"). However, it doesn't work with two arguments : > FireEvent("onKeyUp",event). > > But It works without a problem with comtypes. > > See the following example to reproduce and co

[python-win32] FireEvent : comtypes work but win32com fails, why?

2008-06-24 Thread June Kim
IE's FireEvent works with a single argument, for example, FireEvent("onKeyUp"). However, it doesn't work with two arguments : FireEvent("onKeyUp",event). But It works without a problem with comtypes. See the following example to reproduce and compare: file: c:/temp/javascripttest/onkeyup.html

Re: [python-win32] Querying the VNC Service fails sometimes

2008-06-24 Thread Mark Hammond
> For some reason, after upgrading to 211, I am getting > an > import error on my wx module. Are these tied together in some weird > way? Not that I can think of, and build 211 didn't add any funky new import tricks or anything. However, build 211 is packing the MFC DLL now, so *that* could be re

[python-win32] import cx_Oracle in ASP

2008-06-24 Thread Tibor Arpas
Hi, I'm trying to connect to database from ASP. I reduced my source to the following snippet: <%@ LANGUAGE = Python%> <% import sys for s in sys.path: Response.Write(s) Response.Write("") import cx_Oracle %> After invoking the asp page I get the following result: C:\ActivePyth

Re: [python-win32] Querying the VNC Service fails sometimes

2008-06-24 Thread Mike Driscoll
Kevin, Also check the permissions on the problem users registry. I would expect that to cause a different error, but it might be worth checking. Most users are local admins. And it's just been happening for the last couple of weeks, so it's likely what Roger said: a corrupt registry entry.