Charles,
there's probably a wiser way to do it than the one I'll tell you now.
Put all your key handling functions in a button, use the button as
frontscript, it will trap everything, remember to pass the messages
to the rest of the message path or your keys will stop working.
cheers
andre
On Nov 4, 2005, at 5:30 PM, Charles Hartman wrote:
I should know this, but I can't locate talk I think I've heard
about it:
I've got a (sub)stack with a couple of buttons and a scrolling,
list-behavior field that covers most of the card. I want command-
key alternatives to pressing the buttons. I put handlers in the
stack script for the commandKeyDown, returnKey, and escapeKey
messages, and they work fine -- as long as the focus is outside the
list field. So in the list field's script I put handlers for
returnInField, escapeKey, and rawKeyDown with an "if" test for
"commandKey is down". Those work fine too. But this seems silly;
I'm duplicating code.
Is there a property I should be setting to make the field not grab
(for example) the cmd-A to "select all" lines in the field, or the
return key and swallowing it? While still letting arrow keys and
mouse-clicks select a line? Or is there another simple way to
consolidate this? I'm sure there is, but I can't seem to find it . . .
Charles Hartman
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
