thanks Ricardo,
I interacted with the table because I didn’t know you can read the list with up
and down arrows while quick nav is off.
This helps a lot. Thank you.
Antonio
> On Oct 8, 2015, at 2:02 AM, Ricardo Walker wrote:
>
> Hi,
>
> Why interact with the table?
Hi,
Why interact with the table? There is no need. Just arrow down through the
list. You will also want to make sure the window is expanded go to the windows
menu and hit zoom.
hth
> On Oct 8, 2015, at 1:55 AM, Antonio Guimaraes wrote:
>
> Hi all,
>
> Using right Owl,
Hi,
In El Capitan, the VoiceOver command to jump to the top has changed. It no
longer uses the shift key. So VO+home now takes you to the top and VO+end takes
you to the bottom. If you add the shift, you are taken to the first and last
visible item.
Robert Carter
> On Oct 8, 2015, at 8:36
Not sure if this is a new bug, but I’ve also noticed that it seems to be
impossible to jump to the top of the table with voiceover command, options shit
left arrow. Can anyone confirm this?
> On Oct 8, 2015, at 2:21 AM, Antonio Guimaraes wrote:
>
> thanks Ricardo,
>
> I
Just as an aside, not interacting normally works. In Mail, you don't need to
interact with the messages or mailboxes tables; in Finder, you will be able to
browse folder/file lists without interacting, same for the sidebar; in
Messages, you can arrow through the conversations table without
I'd also add that, as with most places in OS X, option-up or option-down will
move to the top or bottom of the table. You may need to stop interacting first,
but after that those commands will work. They are less keystrokes than the VO
commands, but they only work in tables; the VO commands
Sent: Thursday, October 8, 2015 9:37 AM
To: macvisionaries@googlegroups.com
Subject: Re: Night Owl interrupts messages
Not sure if this is a new bug, but I’ve also noticed that it seems to be
impossible to jump to the top of the table with voiceover command, options shit
left arrow. Can anyone
Hi all,
Using right Owl, I switch to list view, then interact with the table of
messages.
Most of the time the messages won’t read with VoiceOver in their entirety.
Seems there’s a time limit for how long each message will be read for.
I don’t seem to experience this problem from my timeline.