Re: preventWindowOrdering
Re: preventWindowOrdering
- Subject: Re: preventWindowOrdering
- From: Brian Webster <email@hidden>
- Date: Tue, 12 Mar 2002 14:03:52 -0600
On Tuesday, March 12, 2002, at 12:28 PM, Andreas Schwarz wrote:
When I call [super mouseDown:] in my view, the app gets trapped
there until a mouseUp -- and not the mouseUp that corresponds
to the mouseDown that started the whole thing... the next
mouseUp that occurrs after THAT. Then it comes out of [super
mouseDown:] and continues on its merry way... except, of
course, this wreaks total havoc with the event stream in my
app! Not to mention the user's clicks do things that seems to
make no sense.
<snip stack trace>
Wow, that's supremely bizarre. Especially the three calls to
-[NSEvent dealloc]. Does this same thing happen if you don't
call -[NSApplication preventWindowOrdering], i.e. your
mouseDown: does nothing but call super?
--
Brian Webster
email@hidden
http://homepage.mac.com/bwebster
_______________________________________________
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.