Admitedly, I did find the key combination a bit much at first, but I
have made extensive use of the num pad commander. I still have to use
some V O commands, but not as many. Granted, this doesn't help when
using a laptop, but at least the entire key set doesn't have to be
reconfigured because of the lack of a num pad.
On Nov 14, 2008, at 11:15 PM, Jacob Schmude wrote:
Perhaps what would be best is to make the VO key, or keys, user-
configurable. Come to think of it, all the commands should be user-
configurable. I like the vo keys personally, as they stay out of the
way of my application keys. But I can see how not everyone would,
and I think providing a configuration option would solve both
issues--I want the VO keys the way they are, you want to change
them. We could have our cake and eat it too :).
On Nov 15, 2008, at 00:11, David Truong wrote:
I truly think Voice-over should change the vo-keys to be vo-key.
To me it's
ridiculous to have to press two keys before you've even pressed
another key
making it 3 just to activate a screen reading command. Ah well,
you guys
have gotten use to other such stupidities before. So I guess I'll
have to
as well if I want to use the mac smile. Please don't flame me as I
still
love my mac pro smile. But I just hate having to press more keys
than I
should.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jacob
Schmude
Sent: Saturday, 15 November 2008 11:04 AM
To: General discussions on all topics relating to the use of Mac OS
X by
theblind
Subject: Re: webkit
Hi Esther
Actually ,they do work, but there as been a change in the Webkit code
base. For access keys, you must now press ctrl+option and the letter.
Needless to say this is annoying as all get out, as it interferes
with
just about every Voiceover key combination around.
On Nov 14, 2008, at 19:58, Esther wrote:
Hi Mike,
Yes, if you start up WebKit it will look as though Safari is
running, except that things like VO-Shift-M on Web page links will
bring up the contextual menu and other such fixes. You really are
running Safari, but the underlying engine powering it has some
fixes. On the slightly negative side (for me), the access keys for
the Mail Archive site for this list at:
http://www.mail-archive.com/[email protected]/
don't work under WebKit right now, so I can't use Control-I to shift
the list of posts to a set of links indexed by date, and Control-C
to shift the listing back to links ordered by content into threads.
(Or navigate through threads to read the next post with Control-n
and the previous post with Control-p; or use the analogous commands
of Control-f and Control-b to move forwards or back by date). This
went away in September, but the fix will appear in an upcoming
WebKit build. Until then, I fire up Safari to read and search the
Mailing List archives for this list, but use WebKit for most
everything else web-related.
Cheers,
Esther
On Nov 14, 2008, at 2:13 PM, Mike Arrigo wrote:
Hi everyone. I decided to give the latest nightly build of web kit
a try, one thing I noticed, when running the webkit application, it
shows as safari, and even calls itself safari 3.1, is safari still
loading but using the newer web kit engine instead? So far, it's
working really well.
