From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dukecmmtar02.coxmail.com (dukecmmtar02.coxmail.com [68.99.120.49]) by speech.braille.uwo.ca (Postfix) with ESMTP id B305710A85 for ; Mon, 25 Aug 2008 06:00:42 -0400 (EDT) Received: from [192.168.0.100] (really [70.166.17.50]) by dukecmmtar02.coxmail.com (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20080825100043.XMMI27277.dukecmmtar02.coxmail.com@[192.168.0.100]> for ; Mon, 25 Aug 2008 06:00:43 -0400 Message-ID: <48B282CA.4040207@baechler.net> Date: Mon, 25 Aug 2008 03:00:42 -0700 From: Tony Baechler User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: "Speakup is a screen review system for Linux." Subject: Re: Saving Settings? References: <20080825033420.GA27649@localhost.localdomain> In-Reply-To: <20080825033420.GA27649@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.11 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: Mon, 25 Aug 2008 10:00:43 -0000 Gregory Nowak wrote: >> Seemed that a while ago if you changed a parameter-and-it were >> out-of-range, it would mention its alowd values. >> > > It still does. If you didn't get an error, then your value must have > been correct. Whether you actually see the effects of the new value is > a different matter, but I just checked to be sure, and you are still > told what the valid range for a parameter is if you've put in the > wrong value. > Hmm, that's very interesting. I have tried this with the 3.0.2 20080517, 3.0.3 20080724 and my own git pull from earlier in August. I can write anything I want to the files in /sys/module/speakup/parameters and I get no errors. I thought the same as you, but it left the value as it was before, not what I put in. I was playing with the trigger_time as per Samuel's suggestion. I had no idea what the allowed range was so I just started echoing numbers. I could echo 999 >trigger_time and I got no error, but "cat trigger_time" gave me 25 or something like that. If I echoed 0, it still remained at 25. I finally discovered from trial and error that 10 seemed to be about the lowest I could go without getting errors. Maybe for pitch, rate, and volume it works better. On the other hand, if I use the Speakup keys to adjust rate and volume, it beeps when it hits the max rate and wraps around to 0 after it hits volume 9. I only discovered that by accident because I was using the 3.0.2 20080517 version with the bug not letting me write to the parameters files directly.