Ah, sorry. I wasn't sure, so thought I'd double-check. Are the shift commands 
with space different from the ones without the shift? i.e. shift-space-h versus 
space-h. That is a good point. When I considered buying this display, I 
realized after looking at the manual that Apple commands wouldn't be supported 
widely by FS. All of the commands in the manual are Jaws or windows-based. I 
don't have a particular problem with this, given that the Mac is off-the-shelf 
and FS is primarily working with jaws and windows, naturally. Getting the 
firmware updates is a bit tricky, too, but doable.

It seems that this shift-key implementation might be a good suggestion for 
Apple devs to make use of. This gives two more modifier keys to play with.

Teresa
On Oct 4, 2013, at 8:01 AM, Ben van Poppel <benvanpop...@gmail.com> wrote:

> Hi Teresa.
> 
> Sorry, I should have been a bit more explicit. I meant, when you're assigning 
> commands in the Braille tab, you can assign keystrokes including the shift 
> keys, provided the keystroke also includes the spacebar, but not otherwise. 
> I'm assuming it has to do with how VO reads the key events from the Focus, 
> ie., something like if perkins keys are pressed, only treat the keystroke as 
> a VO command if space is held down as part of it, otherwise translate to a 
> typable character. I had wanted to assign commands like focus right shift +h 
> to go to next heading, left shift +h to go to previous, or even to redefine 
> dot7 and dot8 as backspace and enter respectively. It just seems unduly 
> restrictive for no good reason.
> 
> Ben
> 
> 
> On 05/10/2013, at 12:36 AM, Teresa Cochran <vegaspipistre...@gmail.com> wrote:
> 
>> Hi, Ben,
>> 
>> I have a Focus 40 Blue. I admit that I have never tried to use the shift 
>> keys when assigning keystrokes. Have you tried this yet? I'd think it might 
>> be worth a shot. Go into VO utility with VO-f8 and choose Braille. Then 
>> choose the Display tab and once you have your display selected, press the 
>> assign commands button and have a go at it. You can also look up the 
>> previously-assigned commands in the table.
>> 
>> HtH,
>> Teresa
>> On Oct 4, 2013, at 6:50 AM, Ben van Poppel <benvanpop...@gmail.com> wrote:
>> 
>>> Hi everyone.
>>> 
>>> Just wondering if anybody else has encountered this. Since the beginning 
>>> I've used VO on the Mac with my faithful old Focus 40 display, which 
>>> rattles ominously now but is still going strong after 7 years. The shift 
>>> keys on either side of the spacebar on the Focus's Perkins keyboard don't 
>>> seem to have been made bindable in any way using VoiceOver, except they 
>>> seem to emulate a shit modifier from the actual keyboard. More precisely, 
>>> if pressed with space + other keys, they are useable as part of a command, 
>>> otherwise they behave like regular shift keys. This never bothered me since 
>>> I was using a desktop keyboard and could go to town with the numpad 
>>> commander. Now I've purchased a Focus 40 Blue to use with my MacBook Air 
>>> and i-thingies. The shift keys on the Blue don't do anything either, which 
>>> cramps my style a little more. Of course JAWS always bound them into useful 
>>> keystrokes, and Brltty under Linux uses them as well. I'm curious as to why 
>>> Apple hasn't at least made them available so they can be assigned to do 
>>> useful work, ie., act as full command modifiers in their own right. Has 
>>> anybody else experienced this and/or know if there's a reason they haven't 
>>> been fully taken advantage of? More for my own interest than anything, but 
>>> I might run it by Apple if nobody knows the answers on here or its not 
>>> already an anomaly Apple knows about.
>>> 
>>> Cheers.
>>> Ben
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "MacVisionaries" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to macvisionaries+unsubscr...@googlegroups.com.
>>> To post to this group, send email to macvisionaries@googlegroups.com.
>>> Visit this group at http://groups.google.com/group/macvisionaries.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "MacVisionaries" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to macvisionaries+unsubscr...@googlegroups.com.
>> To post to this group, send email to macvisionaries@googlegroups.com.
>> Visit this group at http://groups.google.com/group/macvisionaries.
>> For more options, visit https://groups.google.com/groups/opt_out.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to macvisionaries+unsubscr...@googlegroups.com.
> To post to this group, send email to macvisionaries@googlegroups.com.
> Visit this group at http://groups.google.com/group/macvisionaries.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to macvisionaries+unsubscr...@googlegroups.com.
To post to this group, send email to macvisionaries@googlegroups.com.
Visit this group at http://groups.google.com/group/macvisionaries.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to