Michael Curran schrieb:
> Thanks.
>
> Interested to know what the timeframe is now in regards to getting
> dyndispatch merged in to trunk? I've been trying dyndispatch as a
> replacement to win32com IDispatch for my own project, and performance
> is just the same, if not a little better.
>
> Were there any other features that needed to be added? I'm certainly
> happy with how it is at the moment.
What I have added a few days ago was a way to access constants in a type library
from objects exposing IDispatch::GetTypeInfo() and ITypeComp (in the dyndisp
branch).
It works for early bound, late bound, and lazy bound objects (are these correct
names to a native english speaker?).
There is now a function (actually a class) named comtypes.client.Constants.
It can be used in this way:
>>> from comtypes.client import CreateObject, Constants
>>> x = CreateObject("Excel.Application")
>>> c = Constants(x)
>>> c.xlSaveChanges
1
>>> c.xlDoNotSaveChanges
2
>>>
A nice improvement would of course be to make events (ShowEvents,
GetEvents) work without generating the typelib wrapper, but that is too
much work at the moment. Don't you need it?
> I'd be happy to help with writing tests and or documentation if that is
> something that has to be done before merging --- Obviously I am quite
> keen to see this merged :)
My original plan was to work on compatibility with Python 3, and release then,
but if you're really waiting for it I can as well release now.
> Mick
Thomas
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
comtypes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/comtypes-users
