I do actually want to use these non-COM interfaces from python.
You can see these interfaces as a sort of callback-functions. I want to 
implement them in python an receive calls from the COM-object on it (after 
passing a pointer to it to the COM object).
(I do know there are other ways in COM to do eventing...)
I successfully can use the COM object from python and call COM methods on it. 
But using these non-COM interfaces are causing toubles.
I will try an patch my comtypes and see where it takes me.
Thank you

-----Original Message-----
From: Thomas Heller [mailto:thel...@ctypes.org]
Sent: vrijdag 11 april 2014 14:46
To: comtypes-users@lists.sourceforge.net
Subject: Re: [comtypes-users] Why is a baseinterface mandatory?

Am 11.04.2014 14:33, schrieb Houtekier, Thomas:
> Yes, that is probably the case for COM. But in idl, you can define an
> interface that is not a COM interface. There is nothing preventing you
> to do that. In my case, I have a idl where there are a few
> COM-interfaces defined, but also a few 'normal' (=not COM) interfaces.
> For my use-case it doen't make sense to make them COM-interfaces. They
> are not mend to be used like this. Why does the
> comtypes.client.GetModule ('myTlb.tlb') not allow this? Is there maybe
> a technical reason for it or is it a choice?
>

Ok, so it seems your idl makes sense (for you, at least ;-).
But you don't want to access these non-COM interfaces from Python, don't you?

If this is the case, you should probably patch the code generator to allow 
non-COM interfaces and delete the generated code for them afterwards. Something 
like this...

In other words, I disallowed these interfaces because I never encountered them 
(and comtypes would probably become confused about them).

Thomas




------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration Continuously Automate 
Build, Test & Deployment Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
comtypes-users mailing list
comtypes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/comtypes-users
This message is subject to the following terms and conditions: MAIL 
DISCLAIMER<http://www.barco.com/en/maildisclaimer>

------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment 
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
comtypes-users mailing list
comtypes-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/comtypes-users

Reply via email to