[BRLTTY] Getting my braille driver for the FCHAD working.

[timothyhobbs at seznam.cz]

Well I know I could.  But I'm not sure if I should.  The reason I need to 
know is that I have a row of touch sensors, and I need to be able to figure 
out which sensor is being touched.  Imagine you have sensors 1 2 3 4 5 6 and
2 3 and 5 are being triggered.  If you know that the user is using their 
right hand, then you are able to guess that they mean to touch 2.  If they 
are using their left hand however, then they are probably trying to touch 
sensor 5.  I want it to be easy for the user to choose which hand to use and
to switch hands which makes a cli argument to the driver seem appealing.  
Perhaps if I make it so you change the handedness by sending an argument to 
brltty when you start it, and then the device will save that setting and 
keep it until it gets changed again.  But then again, I realise that the 
blind users of this device aren't going to have a very easy time sending CLI
arguments to brltty and restarting brltty when they need brltty to interface
with the computer.  I mean I could add a physical switch to the device :)  
Would you like that?




Timothy  
---------- Původní zpráva ----------
Od: S. Massy <lists at wolfdream.ca>
Datum: 18. 10. 2012
Předmět: Re: [BRLTTY] Getting my braille driver for the FCHAD working.
"On Thu, Oct 18, 2012 at 08:37:04PM +0200, timothyhobbs at seznam.cz wrote:
> Things are going pretty well in the development.  I can now send and 
receive
> frames and process them correctly.  One question.  I have to figure out if
> the user is left handed or right handed.  This is not yet defined by the
> standard that I wrote.  There are several options:  brltty could provide
> this information, and this information could be global to brltty.  My 
driver
> could take a special parameter or save a special settings file to the 
users
> home directory.  This information could be stored on the device.  What do
> you recommend?
What's your use-case? Need it be automatic? 

Since you're designing the device and firmware as well, you could make
it user-cnfigurable on the device, and then it could be passed as a
parameter to the driver along with model ID, cell count, and so forth in
the handshake.

OTOH, if it's just a matter of using different key-bindings, you could
just write alternate kti files.

Cheers,
S.M.
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY at mielke.cc
For general information, go to: http://mielke.cc/mailman/listinfo/brltty
(http://mielke.cc/mailman/listinfo/brltty)"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mielke.cc/pipermail/brltty/attachments/20121018/a39ff789/attachment.html>