#173 Create object fails to instantiate an MS OneCore object

[Anonymous]

The following suggests an issue with the creattion of an instance. Important because MS is moving many of their desktop technologies to OneCore.

namespace path twapi
(bin) 55 % comobj SAPI_OneCore.SpVoice
No such interface supported

Note: Tcom returns a valid handle.
Win10

[Ashok P. Nadkarni]

Can you not use sapi.SpVoice (comobj sapi.SpVoice) ? That works for me. Note Sapi_OneCore does not support the Automation interface which is required by TWAPI.

I'm not familiar at all with the SAPI architecture so I'm not sure what you might lose using sapi instead of Sapi_OneCore.

/Ashok

[Anonymous]

Sorry it took so long to reply.
Looking at the registry, OneCore speech references SAPI.dll. However, don't know how long that is going to last. Most of the docs are not difficult to locate. However, I thought that TCOM used the automation interface. That did return a valid handle.

On another note-what are the implications for TWAPI at it relates to UWP.

[Ashok P. Nadkarni]

Re. UWP, I really don't know yet as first have to figure out how Tcl would compile for UWP.