[Kde-accessibility] KTTSD does not speak, no way to debug
Robert Vogl
voglrobe at web.de
Thu Jul 29 22:07:06 CEST 2004
Am Donnerstag, 29. Juli 2004 16:34 schrieb Gary Cramblitt:
> On Wednesday 28 July 2004 02:18 pm, Robert Vogl wrote:
>
> Thank you for the feedback.
Hello Gary,
> > I configured it for use of "Hadifax" (AFAIK a typo here, correct is
> > "Hadifix") and the "Test" function of the kttsmgr-properties tab
> > performes well. My sentence to speak is listed in the Job View.
>
> Did you remember to also do "dcop kttsd kspeech startText 0"? setText
> creates a text job but it doesn't start until you call startText.
Yes, I did (I know the kspeech API, because I plan to write a KTTSD plugin for
KSayIt).
> Did you remember to click the Default button in kttsmgr after configuring
> Hadifax? There must be a check mark next to Hadifax indicating it is the
> default talker.
Yes, there is a check mark.
> The best way to debug is 1) start kttsd in a konsole, 2) in a separate
[...]
> It is possible to configure kdDebug to output to a file. Run "kdebugdialog
> --fullmode".
Thanks for your hints. I will follow your advices and contact you if I got an
idea what's going wrong.
> FYI, KTTSD is undergoing major refactoring right now to better support
> asynchronous plugins. I will be posting enhanced APIs in a few days.
Good to know.
Greetings,
--
Robert Vogl
voglrobe at web.de
More information about the kde-accessibility
mailing list