Re: [python-win32] has the COM interface capability changed since 1999

2014-05-14 Thread mc@mclaveau
Hi! Warning! The APIs (almost-COM a not COM) of Dragon NaturallySpeaking change (very) often, depending of version of software. A software who run OK with version 11 don't run with version 12. And more... ??? @-salutations -- Michel Claveau ___

Re: [python-win32] has the COM interface capability changed since 1999

2014-05-14 Thread Mark Hammond
I also meant to mention that pythoncom has grown support for vtable-based *incoming* interfaces - eg, used by content-sinks/event-handlers - so if Dragon has partial support for IDispatch-based interfaces you might be OK. Mark On 14/05/2014 3:37 PM, Mark Hammond wrote: On 13/05/2014 2:57

Re: [python-win32] has the COM interface capability changed since 1999

2014-05-13 Thread Mark Hammond
On 13/05/2014 2:57 PM, Eric S. Johansson wrote: back in 1999ish, joel gould wrote the following and I want to know if it is still true. am planning on converting the 2.7ish natlink to 3.X some time over the next year. need to decide if I should leave the C++ code alone or can we go pure python?

[python-win32] has the COM interface capability changed since 1999

2014-05-12 Thread Eric S. Johansson
back in 1999ish, joel gould wrote the following and I want to know if it is still true. am planning on converting the 2.7ish natlink to 3.X some time over the next year. need to decide if I should leave the C++ code alone or can we go pure python? - The first step