[jawsscripts] Re: Layered Keys
- From: "Raymond Lombardi" <ray214@xxxxxxxxx>
- To: <jawsscripts@xxxxxxxxxxxxx>
- Date: Fri, 11 May 2012 11:39:06 -0400
Is there anyway you guys can make a script for the program cyber link power
to go?
I use it for burning cds.
--------------------------------------------------
From: "Bissett, Tom" <tom.bissett@xxxxxxx>
Sent: Friday, May 11, 2012 11:37 AM
To: <jawsscripts@xxxxxxxxxxxxx>
Subject: [jawsscripts] Re: Layered Keys
> The babble about "Conversation not asigned" is because this particular
> key stroke/combo is assigned to I believe a msn chat or something script.
> The only place I can find actual reference to the layer is a function in
> the default .jss "KeymapChangedEvent" where it is used to produce that
> lovely little sound.
> I like the idea of having a miriad of new keystrokes but as others have
> said it would be nice to be able to stay in layered mode until you wish to
> exit thus retaining control over keystrokes.
> I don't know whether it would be posible to capture the layer and hang on
> to it until your are done.
>
> Regards
> Tom Bisset
> -----Original Message-----
> From: jawsscripts-bounce@xxxxxxxxxxxxx
> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Geoff Chapman
> Sent: May 11, 2012 11:06 AM
> To: jawsscripts@xxxxxxxxxxxxx
> Subject: [jawsscripts] Re: Layered Keys
>
> hmmm, forgetting for a moment the issue of an unrecognized key being
> passed
> along to the underlying app as it leaves the layer, Which by the way I
> would
> also agree optimally ought not to happen,
> I'm not even sure I feel personally that such an unrecognized key should
> be
> permitted to exit the layer at all! What's the sense in that? wouldn't it
> be more optimal to trap anything that isn't a recognized scripted layer
> keystroke, and only allow exiting from the layer through hitting either
> escape, or a recognized layered Key?
> Furthermore, I'm also bothered by the fact of the insert+Top
> Row 1 keyboard help, appearing at present,
> not to have been supported inside a layer.
>
> I Mean, Is there any real practical reason for that?
> or is it just incomplete programming.
>
> At present, in jaws11, when I press Insert+1 inside my Jaws+SpaceBar
> layer,
> from my Desktop,
> I hear, Conversation not asigned. After which it promptly exits the
> Layer.
> And I've got no easy way now, of finding out what the goodness that's
> supposed to be about!
> Why the dickens wouldn't they have left alone, the Jaws+Top Row 1 key, to
> activate keyboard help inside layers?
>
>
> ----- Original Message -----
> From: "Soronel Haetir" <soronel.haetir@xxxxxxxxx>
> To: <jawsscripts@xxxxxxxxxxxxx>
> Sent: Wednesday, May 09, 2012 4:03 PM
> Subject: [jawsscripts] Re: Layered Keys
>
>
>> Hrmm, I would almost send that to FS as a bug. I could see having any
>> unrecognized key exit the layered mode, but that key should be
>> swallowed, not sent along.
>>
>> On 5/8/12, Jim Snowbarger <Snowman@xxxxxxxxxxxxxxxx> wrote:
>>> I have not made heavy use of layered keys yet, since I'm still pretty
>>> committed to backward compatibility, out of necessity.
>>> But, it's a very clever concept, and makes wonderfully efficient use of
>>> precious hotkey real estate.
>>> But, I'm afraid I have a love hate relationship with them.
>>> In addition to the efficiency, I love how smoothly they exit the layer
>>> when
>>> you press a key not defined for the layer, and pass the undefined key
>>> straight along to the script or applicaition.
>>> The thing I hate about them is how smoothly they exit the layer when you
>>> press a key not defined for the layer, and pass the undefined key
>>> straight
>>> along to the script or applicaition.
>>>
>>> If that sounded like a cut and paste, it's because it was.
>>> This mechanism is great for automated programs, but maybe a little less
>>> so
>>> for flakey people.
>>> In cases where you can cause unwanted things to happen by issuing
>>> inadvertent key presses, It's a bit dangerous to be happily mucking
>>> around
>>> inside the layer, only to exit it by accident, and start issuing what
>>> you
>>> think are layer keys, but which are actually back in the main layer.
>>> So, is there a way to trap in a layer? What I want to do is, if the
>>> user
>>> enters the layer, require them to declare that they are done with it by
>>> pressing an exit key.
>>> Or, at a minimumk have an event that runs when the layer exists, so I
>>> can
>>> make them aware.
>>> Is there any way to do that?
>>>
>>>
>>> .
>>> The thing that is annoying me right now
>>> __________
>>>
>>> View the list's information and change your settings at
>>> //www.freelists.org/list/jawsscripts
>>>
>>>
>>
>>
>> --
>> Soronel Haetir
>> soronel.haetir@xxxxxxxxx
>> __________
>>
>> View the list's information and change your settings at
>> //www.freelists.org/list/jawsscripts
>>
>>
>
> __________
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
> __________�
>
> View the list's information and change your settings at
> //www.freelists.org/list/jawsscripts
>
__________�
View the list's information and change your settings at
//www.freelists.org/list/jawsscripts
Other related posts:
