public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: speakup@braille.uwo.ca
Subject: Re: how to tell which synthesizer is active
Date: Tue, 8 Sep 2009 10:12:35 -0500	[thread overview]
Message-ID: <20090908151235.GA24861@linux1> (raw)
In-Reply-To: <14244.1252384580@ccs.covici.com>

On Tue, Sep 08, 2009 at 12:36:20AM -0400, covici@ccs.covici.com wrote:
> I want to do this only at boot time, but this sounds like it could have
> a lot of false hits.  I still think the synth could be set to none when
> this happens -- any reason why not?
 
 Hi John,

When we deactivate speakup because of too many timeouts, we don't
actually release the synthesizer.  What we do is similar to what happens
when print screen is pressed.

The code does not set the synth parameter to none in this case because
the synthesizer driver is still active in the system, it is just waiting
for you to press print screen before it starts sending data to the
synthesizer.

I could change the code so that it actually releases the synthesizer
when it deactivates, but, if I do that, you would have to use talkwith
or some other method to activate your synthesizer if speakup deactivates
because of timeouts, which is probably not what you want.

The other change I might be able to make would lead to the synth parameter being
none whenever the synth is deactivated or released including when print
screen is pressed.  What do you think?

William


  reply	other threads:[~ UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 covici
 ` Tony Baechler
   ` How to Tell Which Synthesizer is Active? Hart Larry
     ` Tony Baechler
   ` how to tell which synthesizer is active covici
     ` William Hubbs [this message]
       ` covici
         ` William Hubbs
           ` John G. Heim
             ` William Hubbs
           ` Gregory Nowak
             ` William Hubbs
               ` covici
               ` Gregory Nowak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090908151235.GA24861@linux1 \
    --to=w.d.hubbs@gmail.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).