win32com and Reflection2

Roger Upole rupole at compaq.net
Mon Apr 10 05:34:56 CEST 2000


I had tried that already, but the Reflection2 object did not show up on the
list when I ran the makepy utility.  I assumed at the time that this meant
that
this library was not in a format that makepy could map.  However, after
a look at the docs in makepy, I noticed that it would also take the name
of the .TLB file, so I passed it c:\rwin\r2510e.tlb instead of the library
name.
It worked like a charm !

Conjecture: Couldn't find it by the library name because the RWIN
directory is not on the system path ?
Now I can go back and replace all those hardcoded integer parms :)

If Guido was god, Mark Hammond would be the high saint of win32!
(or the devil's advocate, according to the Unix guys ...)

           Many Thanks,
               Roger Upole

"Mark Hammond" <mhammond at skippinet.com.au> wrote in message
news:s8aI4.48$UB.261 at news-server.bigpond.net.au...
> You should be able to run "makepy" over the reflection object (makepy will
> present a list of objects).  You can find "makepy" on the Pythonwin
> "tools" menu.
>
> Once you have done that and created the Reflection object, the constants
> should be available in win32com.client.constants
>
> eg,
>
> win32com.client.constants.SomeConstantName
>
> Note that the Reflection constants wont appear until you have created the
> reflection object using win32com.client.Dispatch()
>
> Mark.
>
> "Roger Upole" <rupole at compaq.net> wrote in message
> news:WE8I4.100257$ra.2387838 at news.easynews.com...
> >    I'm scripting Reflection2 sessions with win32com.client.Dispatch.
> > However, there are some constants (error codes, transmission modes,
> > etc) in a typelib that I can't seem to get at from the Dispatch object.
> > Anybody know of a way to access these from Python ?
> >    If not, is there any way to get to them from C++ ?
> > I have very little experience with C, but if it is simple I can
> > probably blunder my way through it.
> >              Roger Upole
> >
> >
> >
>
>





More information about the Python-list mailing list