Problems with Rev and Apple's Bluetooth wireless keyboard (??)

[Scott Rossi]

Recently, Howard Bornstein  wrote:

>> I would bet the Bluetooth keyboard is saving power by not transmitting
>> any info to let the machine know when "unimportant" keys such as shift,
>> option, etc. are depressed and released. It probably only sends that
>> info when a "real" key - i.e. one which represents a character - is
>> pressed. 
> 
> Ugh. This would be bad. I often use a "if the shiftkey is down" or an
> "if the optionkey is down" in a mouseup handler to provide special
> features. If you're right, this will no longer work for wireless
> keyboard users.

I empathize with you.  Did you try investigating rawKeyDown to see if *any*
messages are sent?  Hopefully you will find a workaround.

I recently endured some significant headaches (and subsequent embarrassment)
from a client demo that refused to work on Windows.  Had to get everything
working on a Mac at the last minute and apologize to the client for the
apparent lack of functionality in Rev.  After many hours of testing/hair
pulling, the issue turned out to be a malfunctioning keyboard that I only
thought to check on a whim, after much help from this list.

When faced with issues like these, the "Reasons You're A Software Developer"
offer little comfort.  It just goes to show that whatever you build will
*never* work on every system out there and there is no substitute for, as
Klaus Major says, "Test, test, test".

Regards,

Scott Rossi
Creative Director
Tactile Media, Multimedia & Design
-----
E: scott at tactilemedia.com
W: http://www.tactilemedia.com