Re: modifier-flags with no key pressed and mouseDown 256, why?
Re: modifier-flags with no key pressed and mouseDown 256, why?
- Subject: Re: modifier-flags with no key pressed and mouseDown 256, why?
- From: Alexander Reichstadt <email@hidden>
- Date: Sat, 17 Jan 2009 08:51:12 +0100
Thanks for all the input, makes sense.
Alex
On 16.01.2009, at 23:29, Shawn Erickson wrote:
On Fri, Jan 16, 2009 at 1:15 PM, Dave DeLong <email@hidden>
wrote:
My understanding is that the modifierFlag "256" means that no other
modifiers are pressed. I haven't found it in the docs anywhere,
but I
believe that you can count on "256" meaning "no flags". Every
machine I've
tested this on (I've done a bunch of CGEvent stuff recently) seems
to agree.
Unsafe assumption. You are just lucky that some lower bit (device
dependent bit) is being set for you. I know of no documentation that
says this bit will always set. Additionally if some other device
dependent bit is set your assumption would be broken.
-Shawn
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden