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: Fri, 16 Jan 2009 23:07:28 +0100
Thanks Dave, if someone still has a reference or headerfile or can
point me to something from which I can logically deduce that this will
hold true, it would help a lot.
On 16.01.2009, at 22:15, Dave DeLong 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.
Dave
On Jan 16, 2009, at 2:08 PM, Alexander Reichstadt wrote:
Hi,
I have a phenomenon I am exploiting but unless I know for sure why
it works must stop to use. The objective is to make sure that while
the mousebuttons is being pressed no other modifier key is pressed,
if anything is pressed the whole method return. Testing for 256
seems to work, why?
NSUInteger modifierFlags = [currentEvent modifierFlags];
if (modifierFlags!=256) return;
Is there some documentation that supports this test, or do I have
to check for all the different keys not to be pressed instead?
Thanks
Alex
_______________________________________________
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