From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wlym.com (wlym.com [66.135.63.43]) by speech.braille.uwo.ca (Postfix) with ESMTP id 7F7A110A0F for ; Tue, 8 Sep 2009 12:14:41 -0400 (EDT) Received: from ccs.covici.com (pool-70-109-54-11.clppva.fios.verizon.net [70.109.54.11]) (authenticated bits=128) by wlym.com (8.14.3/8.14.3/Debian-5) with ESMTP id n88GEcWd020079 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 8 Sep 2009 11:14:40 -0500 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.3/8.14.2) with ESMTP id n88GEYlk000958 for ; Tue, 8 Sep 2009 12:14:37 -0400 To: "Speakup is a screen review system for Linux." Subject: Re: how to tell which synthesizer is active In-reply-to: <20090908151235.GA24861@linux1> References: <14688.1252299370@ccs.covici.com> <4AA5C28E.6090506@baechler.net> <14244.1252384580@ccs.covici.com> <20090908151235.GA24861@linux1> Comments: In-reply-to William Hubbs message dated "Tue, 08 Sep 2009 10:12:35 -0500." X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.1.1 Date: Tue, 08 Sep 2009 12:14:34 -0400 Message-ID: <957.1252426474@ccs.covici.com> From: covici@ccs.covici.com X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.12 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Sep 2009 16:14:41 -0000 Well, what used to happen is that speakup actually probed and if the synth was not there, then the synth was set to none, but now I guess it does not do that anymore, but I agree that releasing the synth because of timeouts may not be a good idea, but could there be a way to see if the synth is there? William Hubbs wrote: > 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 > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com