Recognition event from SAPI 5.1 in C++ - how to...

Hi,

All I need is for an event to be fired when text is recognized and
converted from speech to text. I am using SAPI 5.1. Unfortunately, the
examples are quite hard to follow, and the help files seem somewhat
opaque. Adding to the confusion, I have to use Borland C++ Buider V6,
and would therefore prefer to use the "raw" COM interfaces.

Can anybody help me out?

Sincerely,

<anders.johansen@gmail.com> wrote in message 
news:d31b653b-9d50-48e0-bd6e-08aa5e3fbfeb@l28g2000prd.googlegroups.com...
> All I need is for an event to be fired when text is recognized and
> converted from speech to text. I am using SAPI 5.1. Unfortunately, the
> examples are quite hard to follow, and the help files seem somewhat
> opaque. Adding to the confusion, I have to use Borland C++ Buider V6,
> and would therefore prefer to use the "raw" COM interfaces.
>
> Can anybody help me out?

I posted what I hoped would be the barest, simplest, smallest console 
application sample to recognize phrases defined in a single grammar on this 
page:

http://msdn2.microsoft.com/en-us/visualc/default.aspx

The link of 1 April is to a page with the code for that sample as well as a 
video that explains it. The link of 25 March is one which explains about 
setting up the development environment, the machine and redistribution.

I go easy on my use of COM (my Niagara falls <g>) in it but I do use ATL's

CComPtr smart pointer. If Borland doesn't include ATL that may be a problem.

FWIW, I _know_ that the free Express Edition of VC++ does not include ATL, 
but I seem to recall running across posts online where the some have 
described using the newly open sourced WTL with the Express Edition. Perhaps 
that gets a smart pointer class like CComPtr which makes the port easy. 
Perhaps not.

Regards,
Will

On Apr 9, 3:11 am, "William DePalo [MVP VC++]"
<willd.no.s...@mvps.org> wrote:
> <anders.johan...@gmail.com> wrote in message
>
> news:d31b653b-9d50-48e0-bd6e-08aa5e3fbfeb@l28g2000prd.googlegroups.com...
>
> > All I need is for an event to be fired when text is recognized and
> > converted from speech to text. I am using SAPI 5.1. Unfortunately,
the
> > examples are quite hard to follow, and the help files seem somewhat
> > opaque. Adding to the confusion, I have to use Borland C++ Buider V6,
> > and would therefore prefer to use the "raw" COM interfaces.
>
> > Can anybody help me out?
>
> I posted what I hoped would be the barest, simplest, smallest console
> application sample to recognize phrases defined in a single grammar on
this
> page:
>
> http://msdn2.microsoft.com/en-us/visualc/default.aspx
>
> The link of 1 April is to a page with the code for that sample as well as
a
> video that explains it. The link of 25 March is one which explains about
> setting up the development environment, the machine and redistribution.

All right - that looks immensely useful.

I expect to use SetNotifyWindowMessage instead of Win32Events, but it
seems there is plenty of code floating around that illustrates this
approach, so I guess I will be OK (until proven wrong).

Thank you very much for your help!

Sincerely,

On 9 Apr., 16:08, "William DePalo [MVP VC++]"
<willd.no.s...@mvps.org>
wrote:
> <anders.johan...@gmail.com> wrote in message
>
> news:48ba4287-e909-4e61-a414-781bf4021d36@m44g2000hsc.googlegroups.com...
>
> > I expect to use SetNotifyWindowMessage instead of Win32Events, but it
> > seems there is plenty of code floating around that illustrates this
> > approach, so I guess I will be OK (until proven wrong).
>
> It is almost as easy. The "trouble" with that approach in a
sample is that
> as soon as it is decided to use window messages then you need the
> boilerplate for creating the window, pumping messages and handling clicks.

Luckily I already have that, which is why I prefer that solution. I
already use window messages for various other events, so adding
another should be easy.

<anders.johansen@gmail.com> wrote in message 
news:48ba4287-e909-4e61-a414-781bf4021d36@m44g2000hsc.googlegroups.com...
> I expect to use SetNotifyWindowMessage instead of Win32Events, but it
> seems there is plenty of code floating around that illustrates this
> approach, so I guess I will be OK (until proven wrong).

It is almost as easy. The "trouble" with that approach in a sample is
that 
as soon as it is decided to use window messages then you need the 
boilerplate for creating the window, pumping messages and handling clicks.

> Thank you very much for your help!

You are welcome.

Regards,
Will