Re: NSTableView setDoubleAction/NSControl setAction
Re: NSTableView setDoubleAction/NSControl setAction
- Subject: Re: NSTableView setDoubleAction/NSControl setAction
- From: Angela Brett <email@hidden>
- Date: Wed, 7 Aug 2002 21:51:00 +1200
I find this hard to believe. Because it means in effect that I have
to implement my own 'turn two single clicks into a double click'.
Done correctly I should get the user's mouse settings from
somewhere. It is all very non-OO. The delay looks more like having
to find and load the information to me. This click/doubleclick stuff
is very deep inside the frameworks (NSEvent), it is completely
unbelievable I should have to implement this at the app level.
Well, the frameworks are not psychic... how can they know whether the
user is going to click again? The only way for NSEvent to do it for
you is if it always waited a while before sending the single click
action, and that would make things slower and also a bit more
complicated in the many cases where the first click of a doubleclick
does do the same thing as a single click.
I've been reading a book about programming for Windows 3.1 at work
(ugh) and it just happens that I read a passage about this very
issue a few days ago.
I can believe it works like this for Windows 3.1 though. It has been
a while, but that was about the worst API I have ever seriously
programmed for. But seriously, you take a Windows 3.1 programming
guide as the basis for Cocoa behaviour?
No, I don't... in general I use the Windows 3.1 programming guide as
a reminder of how good Cocoa is, and also as a way to get money. :) I
was just mentioning that because it was an interesting (or not)
co-incidence.
--
Angela Brett
email@hidden
http://acronyms.co.nz/angela
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.