Jeanne A. E. DeVoto wrote:
At 2:38 PM -0700 11/2/2007, Richard Gaskin wrote:
If what I'm seeing is true, Rev does not send the menuPick message
when an option control has a new value selected via these keyboard
shortcuts.
I'm seeing menuPick here when using the keyboard-only method (Vista
with Rev 2.8.1). Does the menu button have its traversalOn set to
true? That might make a difference.
Yes, the traversalOn is true (not sure how I'd be able to interact with
it via the keyboard without that).
Thank you for looking into this. With your good result I was prompted
to look further, and found the true issue:
The menupick message is indeed being sent, but the menuhistory is not
updated when the control is manipulated via the keyboard as it is with
the mouse.
This simple script let me check this out as I tested:
on menupick
put the params && the menuhistory of the target
end menupick
I've just posted this bug to the QAC:
http://quality.runrev.com/qacenter/show_bug.cgi?id=5505
Any of you using option controls on Windows may want to vote for this,
since unless you've already scripted workarounds you'll find that
relying on the value of the menuhistory may yield bugs in your
application from a mismatch between what the user sees as the control
value and what the engine thinks the control value is.
--
Richard Gaskin
Fourth World Media Corporation
___________________________________________________________
[EMAIL PROTECTED] http://www.FourthWorld.com
_______________________________________________
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
