FROM : Stefan Heukamp
DATE : Tue Apr 03 20:10:28 2007
Thank you all for your answers!!
Andreas' suggestion worked very well so I do not have to rewrite the
drag'n' drop stuff on my own :-)
Am 03.04.2007 um 19:18 schrieb glenn andreas:
>
> On Apr 3, 2007, at 12:05 PM, Nick Zitzmann wrote:
>
>>
>> On Apr 3, 2007, at 10:58 AM, Stefan Heukamp wrote:
>>
>>> Is this a bug or should it work like this?
>>
>> In most built-in NSView subclasses, the -mouseDown: method starts
>> tracking events on its own, so -mouseUp: is never called. So it is
>> not a bug.
>>
>>> If it should work like this is there any other possibility to get
>>> the mouseUp events?
>>
>> You'd have to override -mouseDown: and rewrite most of its
>> functionality yourself. Good luck.
>
> Assuming you just need to do some sort of special processing at
> mouseUp time (which doesn't otherwise alter the behavior implicit
> in the mouseDown code), you could just do this:
>
> - (void) mouseDown: (NSEvent *) theEvent
> {
> [super mouseDown: theEvent];
> // insert custom code that you want to happen after mouse up here
> }
>
>
>
> Glenn Andreas <email_removed>
> <http://www.gandreas.com/> wicked fun!
> quadrium2 | build, mutate, evolve, animate | images, textures,
> fractals, art
>
>
>
DATE : Tue Apr 03 20:10:28 2007
Thank you all for your answers!!
Andreas' suggestion worked very well so I do not have to rewrite the
drag'n' drop stuff on my own :-)
Am 03.04.2007 um 19:18 schrieb glenn andreas:
>
> On Apr 3, 2007, at 12:05 PM, Nick Zitzmann wrote:
>
>>
>> On Apr 3, 2007, at 10:58 AM, Stefan Heukamp wrote:
>>
>>> Is this a bug or should it work like this?
>>
>> In most built-in NSView subclasses, the -mouseDown: method starts
>> tracking events on its own, so -mouseUp: is never called. So it is
>> not a bug.
>>
>>> If it should work like this is there any other possibility to get
>>> the mouseUp events?
>>
>> You'd have to override -mouseDown: and rewrite most of its
>> functionality yourself. Good luck.
>
> Assuming you just need to do some sort of special processing at
> mouseUp time (which doesn't otherwise alter the behavior implicit
> in the mouseDown code), you could just do this:
>
> - (void) mouseDown: (NSEvent *) theEvent
> {
> [super mouseDown: theEvent];
> // insert custom code that you want to happen after mouse up here
> }
>
>
>
> Glenn Andreas <email_removed>
> <http://www.gandreas.com/> wicked fun!
> quadrium2 | build, mutate, evolve, animate | images, textures,
> fractals, art
>
>
>
| Related mails | Author | Date |
|---|---|---|
| Stefan Heukamp | Apr 3, 18:58 | |
| Nick Zitzmann | Apr 3, 19:05 | |
| glenn andreas | Apr 3, 19:18 | |
| Andreas Mayer | Apr 3, 19:33 | |
| Stefan Heukamp | Apr 3, 20:10 |






Cocoa mail archive

