FROM : Scott Anguish
DATE : Wed Jan 30 03:41:58 2008
Yes, sam is quite correct. Please take this off-list
thanks
scott (moderator)
On Jan 28, 2008, at 4:31 PM, Sam Stigler wrote:
> This has gone on long enough. I honestly don't care who's right,
> but can you please take this off-list?
>
> Thank you very much,
>
> Sam
>
>
> On Jan 28, 2008, at 2:59 PM, Hamish Allan wrote:
>
>> On Jan 28, 2008 8:02 PM, Jayson Adams <<email_removed>>
>> wrote:
>>
>>> So yes, he was asking how you get the current mouse location, and
>>> was
>>> believing there's no way to do it.
>>
>> Your willful disregard of the very next sentence after the bit you
>> quoted does not serve to illuminate anything. Here, again, is the
>> whole thing:
>>
>>> (C) How do I know where the mouse is, in the absence of (prior to
>>> receiving) a mouse-related event?
>>>
>>> -- There is not, afaik, any Cocoa frameworks function or method that
>>> gets the mouse location other than from a NSEvent. (It may exist
>>> and I
>>> just haven't found it.)
>>>
>>> -- Getting the current mouse location using Carbon (if there is a
>>> function for that) isn't the answer, because that's going to tell me
>>> where the mouse is *right now in real time*, while the information I
>>> need is where the mouse is *synchronized with the event stream*. (If
>>> I'm about to receive a flood of mouseMoved: or mouseDragged:
>>> messages,
>>> I want to know where the mouse is before them, not after. Unreceived
>>> messages represent the future, I'm still in the present.)
>>
>> I know you think that the real-time location is all that matters, but
>> you are wrong, and I think it's important to make that plain, because
>> you seem to be seeking to obfuscate it.
>>
>> Hamish
>> _______________________________________________
>>
>> Cocoa-dev mailing list (<email_removed>)
>>
>> 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:
>> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>>
>> This email sent to <email_removed>
>
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> 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:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
DATE : Wed Jan 30 03:41:58 2008
Yes, sam is quite correct. Please take this off-list
thanks
scott (moderator)
On Jan 28, 2008, at 4:31 PM, Sam Stigler wrote:
> This has gone on long enough. I honestly don't care who's right,
> but can you please take this off-list?
>
> Thank you very much,
>
> Sam
>
>
> On Jan 28, 2008, at 2:59 PM, Hamish Allan wrote:
>
>> On Jan 28, 2008 8:02 PM, Jayson Adams <<email_removed>>
>> wrote:
>>
>>> So yes, he was asking how you get the current mouse location, and
>>> was
>>> believing there's no way to do it.
>>
>> Your willful disregard of the very next sentence after the bit you
>> quoted does not serve to illuminate anything. Here, again, is the
>> whole thing:
>>
>>> (C) How do I know where the mouse is, in the absence of (prior to
>>> receiving) a mouse-related event?
>>>
>>> -- There is not, afaik, any Cocoa frameworks function or method that
>>> gets the mouse location other than from a NSEvent. (It may exist
>>> and I
>>> just haven't found it.)
>>>
>>> -- Getting the current mouse location using Carbon (if there is a
>>> function for that) isn't the answer, because that's going to tell me
>>> where the mouse is *right now in real time*, while the information I
>>> need is where the mouse is *synchronized with the event stream*. (If
>>> I'm about to receive a flood of mouseMoved: or mouseDragged:
>>> messages,
>>> I want to know where the mouse is before them, not after. Unreceived
>>> messages represent the future, I'm still in the present.)
>>
>> I know you think that the real-time location is all that matters, but
>> you are wrong, and I think it's important to make that plain, because
>> you seem to be seeking to obfuscate it.
>>
>> Hamish
>> _______________________________________________
>>
>> Cocoa-dev mailing list (<email_removed>)
>>
>> 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:
>> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>>
>> This email sent to <email_removed>
>
> _______________________________________________
>
> Cocoa-dev mailing list (<email_removed>)
>
> 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:
> http://lists.apple.com/mailman/options/cocoa-dev/<email_removed>
>
> This email sent to <email_removed>
| Related mails | Author | Date |
|---|---|---|
| quinceymorris | Jan 25, 23:51 | |
| Jayson Adams | Jan 26, 00:38 | |
| quinceymorris | Jan 26, 01:19 | |
| Jayson Adams | Jan 26, 02:43 | |
| Quincey Morris | Jan 28, 01:54 | |
| Jayson Adams | Jan 28, 02:41 | |
| Quincey Morris | Jan 28, 08:46 | |
| Jayson Adams | Jan 28, 18:51 | |
| Clark Cox | Jan 28, 19:24 | |
| Jayson Adams | Jan 28, 19:51 | |
| Hamish Allan | Jan 28, 20:21 | |
| Jayson Adams | Jan 28, 20:26 | |
| Hamish Allan | Jan 28, 20:44 | |
| Jayson Adams | Jan 28, 21:02 | |
| Hamish Allan | Jan 28, 23:59 | |
| Sam Stigler | Jan 29, 01:31 | |
| Wesley Smith | Jan 29, 01:41 | |
| Jayson Adams | Jan 29, 02:26 | |
| Hamish Allan | Jan 29, 14:03 | |
| Clark Cox | Jan 29, 17:23 | |
| John Stiles | Jan 29, 18:36 | |
| Quincey Morris | Jan 29, 19:32 | |
| Scott Anguish | Jan 30, 03:41 | |
| Scott Anguish | Jan 30, 03:43 | |
| Hamish Allan | Jan 30, 06:20 | |
| Quincey Morris | Jan 30, 08:34 |






Cocoa mail archive

