yes, it does. however, if I extend it to a dozen lines or so, it does not.
if I speak then it does, and if I don't, then it does not.
it's entirely erratic, so I can't yet give you an exact reproducible reason
as to when it does not work.
Chip
-----Original Message-----
From: Doug Geoffray [mailto:[email protected]]
Sent: Friday, November 13, 2009 9:03 AM
To: [email protected]
Subject: Re: onCursorKey not working as described
Chip,
No there is no difference. A cursoring key is a cursoring key. The two
liner I gave you to test in Immed also silences cursoring keys in Word.
Doug
Chip Orange wrote:
thanks doug, let me go work up (or down) my code into a managable
example.
does it matter at all that I'm doing this in MS Word? would it work
differently than anywhere else? my script where I noticed this is
associated with Word.
thanks.
Chip
-----Original Message-----
From: Doug Geoffray [mailto:[email protected]]
Sent: Thursday, November 12, 2009 1:18 PM
To: [email protected]
Subject: Re: onCursorKey not working as described
Chip,
For a very simple example, I typed the following two lines in Immed:
function MyOnCursorKey(a, b, c): MyOnCursorKey=TRUE: End Function x
=
ConnectEvent(Application, "OnCursorKey", "MyOnCursorKey")
Once you hit enter on that second line, all cursoring keys go
silent.
So this proves returning True will silence cursoring keys. But be
warned,
until you shut down this event or restart Immed, you will no longer
have any
cursoring keys <smile>.
Doug
Aaron Smith wrote:
On 11/11/2009 6:18 PM, Chip Orange wrote:
how about the example in the onCursorKey
documentation?
There is an example there already.
I think it shows you how you can suppress the normal
window eyes
speech by returning true, and this is what isn't
working for me.
Ah, so you do admit there is an example. <grin> It's working
for me.
That's why I asked for a sample from you.
I already know what I'm doing, but I don't know what you're
doing.
Aaron
