• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: mouseDown vs mouseDragged
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mouseDown vs mouseDragged


  • Subject: Re: mouseDown vs mouseDragged
  • From: Dan Saul <email@hidden>
  • Date: Mon, 14 Mar 2005 10:59:24 -0600

It basically comes down to the fact that mouse down is called once (on
mouse down), and mouse dragged is called multiple times. What you do
depends on the desired behaviour.


On Tue, 8 Mar 2005 14:23:44 -0800, Mark Dawson <email@hidden> wrote:
> Some example code does all mouse tracking through mouseDown; is there
> any recommended division of labor between mouseDown and mouseDragged?
> I assume that you almost always need mouseDown (even if you use
> mouseDragged) to at least store the initial parts of a drag (position,
> if nothing else).
>
> Thanks,
>
> mark
>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list      (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >mouseDown vs mouseDragged (From: Mark Dawson <email@hidden>)

  • Prev by Date: -[NSImage length]: selector not recognized
  • Next by Date: Re: -[NSImage length]: selector not recognized
  • Previous by thread: mouseDown vs mouseDragged
  • Next by thread: objective-c / cocoa efficiency
  • Index(es):
    • Date
    • Thread