From: Luke Yelavich <themuso@themuso.com>
To: speakup@braille.uwo.ca
Subject: Re: An idea,
Date: Thu, 28 Jul 2005 00:45:02 +1000 [thread overview]
Message-ID: <20050727144502.GB10659@localhost.localdomain> (raw)
In-Reply-To: <6.2.3.4.0.20050727092307.0372af40@pop3.citlink.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Jul 28, 2005 at 12:25:06AM EST, Scott Berry wrote:
> This really doesn't pertain to how Gnopernicus works. But one
> question I really would like to through around out here is why are
> the keystrokes so difficult. I know you can change key bindings in
> Gnopernicus but it looked like a guy with 20 years of experience
> would have to do it. Maybe this has changed in recent versions but I
> remember when I started using Gnopernicus wow! Difficult to learn.
I haven't used Gnopernicus regularly for a while now, but I think it is
something to do with the various layers of functionality that
Gnopernicus has. For example, a mouse control layer, a magnification
control layer, a speech configuration layer, etc. I think the idea was
to keep as many keystrokes as possible on the numpad.
As you and others may have found out, this is hopeless when attempting
to use Gnopernicus on a laptop. One has to know how to access their
laptop numpad keys to use Gnopernicus, and then one still has to switch
back and forth between modes while working.
It would be worth while bringing this up on the gnome-accessibility
list, as others may have some ideas about all of this.
- --
Luke Yelavich
GPG key: 0xD06320CE
(http://www.themuso.com/themuso-gpg-key.txt)
Email & MSN: themuso@themuso.com
ICQ: 18444344
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC553ujVefwtBjIM4RAjXBAKDFfrM6MKxIjQpILu43OH63cKSFmACg09HN
GPAAnfZM1eHvPHRDuYNmwss=
=zf/5
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
Murthy T S N
` Luke Yelavich
` Willem van der Walt
` Re[2]: " Farhan
` Gregory Nowak
` Sean McMahon
` shuttle coverage Igor Gueths
` An idea, Lorenzo Taylor
` Kenny Hitt
` Kelly Prescott
` John covici
` Sergei V. Fleytin
` Janina Sajka
` Kelly Prescott
` hank smith
` John covici
` Janina Sajka
` Scott Berry
` Luke Yelavich [this message]
` remapping keys in Gnopernicus was " Kenny Hitt
` Farhan
` Kenny Hitt
` Janina Sajka
` Sean McMahon
` Sean McMahon
` Laura Eaves
` Sean McMahon
` Chris Norman
` Chris Norman
` Kenny Hitt
` Sean McMahon
Sina Bahram
Laura Eaves
` Sina Bahram
` Laura Eaves
` Sina Bahram
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=20050727144502.GB10659@localhost.localdomain \
--to=themuso@themuso.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).